Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-55409 high CVSS 7.6

Cross-Site Scripting (XSS) in filament/forms (CVE-2026-55409)

Summary

Cross-site scripting in filament/forms (CVE-2026-55409). Confidential information can be exposed externally. Exploitable via RichEditor. Mitigation: upgrade to 3.3.53 or later.

Original description

The description as published by the source.

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.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-55409 has been found in filament/forms.
Attackers can target a specific entry point like RichEditor over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.6/10.
What to do: upgrade filament/forms to 3.3.53 or later.
If unsure, ask your IT team or search "filament/forms CVE-2026-55409" on the vendor's site.

CVE-2026-55409 (filament/forms) — CWE-79 / CVSS v3 7.6
Attack vector: remote (network-reachable)
Attack surface: RichEditor
Patched: 3.3.53 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in filament/forms. Attackers reach the vulnerable code path via RichEditor.

📍 Affected scope

Check the vendor advisory for the affected versions of filament/forms. Attack surface: RichEditor.

🔥 Severity

Severity: High (CVSS 7.6/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 3.3.53.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'filament/forms' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'filament/forms' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で filament/forms を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade filament/forms to 3.3.53

    ステージング環境で 3.3.53 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

composer filament/forms
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3.53"}]}]
Packagist filament/forms
[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.3.53"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details