← Back
CVE-2025-52904
high
CVSS 8.0
Command Injection in github.com/filebrowser/filebrowser/v2 (CVE-2025-52904)
Summary
command injection in github.com/filebrowser/filebrowser/v2 (CVE-2025-52904). Successful exploitation can lead to full system takeover. Exploitable via ``grep``. Mitigation: upgrade to `2.33.8` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-52904** has been found in github.com/filebrowser/filebrowser/v2.
Attackers can target a specific entry point like ``grep`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.0/10.
What to do: upgrade github.com/filebrowser/filebrowser/v2 to **2.33.8** or later.
If unsure, ask your IT team or search "github.com/filebrowser/filebrowser/v2 CVE-2025-52904" on the vendor's site.
CVE-2025-52904 (github.com/filebrowser/filebrowser/v2) — CWE-77 / CVSS v3 8.0
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `grep`
Patched: `2.33.8` — 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-77) exists in github.com/filebrowser/filebrowser/v2. Attackers reach the vulnerable code path via ``grep`` without authentication.
📍 Affected scope
github.com/filebrowser/filebrowser/v2 — . Attack surface: `grep`.
🔥 Severity
Severity: High (CVSS 8.0/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2.33.8**.
🛡️ 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 'github.com/filebrowser/filebrowser/v2' .` 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 'github.com/filebrowser/filebrowser/v2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/filebrowser/filebrowser/v2` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/filebrowser/filebrowser/v2 to 2.33.8ステージング環境で 2.33.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/filebrowser/filebrowser/v2
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.33.8"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-52904
- package https://github.com/filebrowser/filebrowser
- web https://github.com/filebrowser/filebrowser/security/advisories/GHSA-hc8f-m8g5-8362
- web https://github.com/filebrowser/filebrowser/issues/5199
- web https://github.com/GoogleContainerTools/distroless
- web https://sloonz.github.io/posts/sandboxing-1
- web https://github.com/sbaresearch/advisories/tree/public/2025/SBA-ADV-20250326-01_Filebrowser_Command_Execution_Not_Limited_To_Scope
- web https://pkg.go.dev/vuln/GO-2025-3793
- web https://github.com/advisories/GHSA-hc8f-m8g5-8362