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. Please note tha…
As published by the sources
Affected packages
- filament/formsAffected
>=3.0.0,<=3.3.52Fixed in3.3.53
Derived from the fixed versions above
What to do
Upgrade filament/forms to 3.3.53 or later.
composer update filament/forms --with-dependencies
To see which version you have installed, run composer show vendor/package. Running composer audit lists the known advisories that match your installed versions.
Quoted from the original advisory
Details
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.
References
- Advisoryhttps://github.com/advisories/GHSA-m9cv-24rx-8mv7
- Webhttps://github.com/filamentphp/filament/security/advisories/GHSA-m9cv-24rx-8mv7
- Webhttps://github.com/filamentphp/filament/pull/20029
- Webhttps://github.com/filamentphp/filament/releases/tag/v3.3.53
- Webhttps://nvd.nist.gov/vuln/detail/CVE-2026-55409