← Back
CVE-2024-51758
Vulnerability in filament/actions (CVE-2024-51758)
Summary
vulnerability in filament/actions (CVE-2024-51758). Risk of unauthorized operations or information disclosure. Exploitable via ``default_filesystem_disk``. Mitigation: upgrade to `3.2.123` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-51758** has been found in filament/actions.
Attackers can target a specific entry point like ``default_filesystem_disk`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade filament/actions to **3.2.123** or later.
If unsure, ask your IT team or search "filament/actions CVE-2024-51758" on the vendor's site.
CVE-2024-51758 (filament/actions) — CWE-1188 /
Attack vector: remote (network-reachable)
Attack surface: `default_filesystem_disk` / `public` / `local`
Patched: `3.2.123` — 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
**A vulnerability** (CWE-1188) exists in filament/actions. Attackers reach the vulnerable code path via ``default_filesystem_disk`` without authentication.
📍 Affected scope
filament/actions — . Attack surface: `default_filesystem_disk` / `public` / `local`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.2.123**.
🛡️ 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/actions' .` 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/actions' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `filament/actions` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade filament/actions to 3.2.123ステージング環境で 3.2.123 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
filament/actions
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.123"}]}]
Packagist
filament/actions
[{"type":"ECOSYSTEM","events":[{"introduced":"3.2.0"},{"fixed":"3.2.123"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-51758
- package https://github.com/filamentphp/filament
- web https://github.com/filamentphp/filament/security/advisories/GHSA-4hxw-gc2q-f6f3
- web https://github.com/filamentphp/filament/commit/19f5347f0e17d9f4eb515e24ea5632031c6829df
- web https://github.com/filamentphp/filament/blob/3.x/packages/actions/src/Exports/Exporter.php#L144-L153
- web https://filamentphp.com/docs/3.x/actions/prebuilt-actions/export#customizing-the-storage-disk
- web https://github.com/advisories/GHSA-4hxw-gc2q-f6f3