You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Filament: Disabled RichEditor field state can be used for XSS
High severity
GitHub Reviewed
Published
Jun 17, 2026
in
filamentphp/filament
•
Updated Jun 17, 2026
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.
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Learn more on MITRE.
In Filament v3, a disabled
RichEditorfield 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
RichEditorso this advisory does not apply.References