CVE-2026-55409: Filament: Disabled RichEditor field state can be used for XSS
In Filament v3, a disabled RichEditor field rendered its raw state without sanitizing HTML. Where the data stored in this field's state isn't sanitized already when the form state was filled, an attacker could plant malicious HTML or JavaScript and achieve XSS that executes for users who view the form.
Published Jun 17, 2026 · Updated Nov 3, 2026
Affected packages
filament/forms
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.0.0, <= 3.3.52
- Fixed in
- 3.3.53
- Check
composer show filament/forms
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
In Filament v3, a disabled RichEditor field rendered its raw state without sanitizing HTML. Where the data stored in this field's state isn't sanitized already when the form state was filled, an attacker could plant malicious HTML or JavaScript and achieve XSS that executes for users who view the form.
Please note that Filament v4 and above does not use the same mechanism for rendering a disabled RichEditor so this advisory does not apply.
Credited to mike197312, danharrin, cookesan.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
