← Back
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.
AI summary snake-internal / snake-material-v2
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`` without authentication.
📍 Affected scope
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 (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'filament/forms' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `filament/forms` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade filament/forms to 3.3.53ステージング環境で 3.3.53 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
filament/forms
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3.53"}]}]