Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
HIGH severity

GHSA-m9cv-24rx-8mv7 — filament/forms

HIGHFix: filamentphp/filament#20029

GHSA-m9cv-24rx-8mv7 is a high-severity (CVSS 7.6) Cross-site Scripting (XSS) vulnerability in filament/forms. A fix is available for filament/forms — see the affected versions and patch details below.

Filament: Disabled RichEditor field state can be used for XSS

Also known asCVE-2026-55409
Published
Jun 17, 2026
Updated
Sep 10, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Sep 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-m9cv-24rx-8mv7.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs19th percentile — riskier than 19% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-m9cv-24rx-8mv7 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected
🐘filament/forms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistfilament/forms≥ 3.0.0&&< 3.3.533.3.53composer require filament/forms:^3.3.53

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for filament/forms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update filament/forms to 3.3.53 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m9cv-24rx-8mv7 is resolved across your whole dependency graph.

  3. Workarounds

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-m9cv-24rx-8mv7 in your dependencies?

Find it across Packagist, including transitive dependencies.

GHSA-m9cv-24rx-8mv7: XSS (High 7.6) | O3 Security