CVE-2026-55409
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFilament is a collection of full-stack components for accelerated Laravel development. From 3.0.0 until 3.3.53, 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. This vulnerability is fixed in 3.3.53.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA stored XSS vulnerability exists in Filament's disabled RichEditor component. From versions 3.0.0 through 3.3.53, disabled RichEditor fields render their raw state without HTML sanitization. If an attacker plants malicious HTML or JavaScript into the field's data before the form is filled, it will execute when users view the form.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Filament versionCheck your composer.json file or run 'composer show filament/filament' to see the exact version number installedAffected if The version is 3.0.0 through 3.3.53 (versions prior to 3.3.54 are vulnerable)
-
Find RichEditor component usageSearch your codebase for uses of \Filament\Forms\Components\RichEditor or the string 'RichEditor::make' in your Livewire components, Filament resources, and form schemasAffected if RichEditor fields are used in your forms
-
Check for disabled RichEditor fieldsIn your form configurations, look for RichEditor fields that have 'disabled' => true set, or that are conditionally disabled via 'disabled' => fn () => ...Affected if Any RichEditor field is configured as disabled (this is the specific attack surface for this CVE)
-
Verify the data flow into disabled fieldsReview how data gets loaded into disabled RichEditor fields; check if the data originates from user-editable sources, databases, or APIs that could contain pre-injected HTML or JavaScriptAffected if Disabled RichEditor fields receive data from sources that could contain unsanitized HTML content
You are affected if your Filament version is between 3.0.0 and 3.3.53 AND you have at least one disabled RichEditor field that could receive unsanitized HTML content from external sources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Filament to version 3.3.53 or later, which includes the HTML sanitization fix for disabled RichEditor fields.
Filament 3.3.53
- Run `composer require filament/filament:^3.3.53` to upgrade to the fixed version
- Verify the upgrade completed successfully by checking your installed version with `composer show filament/filament`
- Clear your Laravel cache with `php artisan cache:clear` to ensure the new version is loaded
- Test that your RichEditor fields render correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-55409 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-55409 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data