Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2025-52903 high CVSS 8.0

Vulnerability in github.com/filebrowser/filebrowser/v2 (CVE-2025-52903)

Summary

Vulnerability in github.com/filebrowser/filebrowser/v2 (CVE-2025-52903). Successful exploitation can lead to full system takeover. Exploitable via find. Mitigation: upgrade to 2.33.10 or later.

Original description

The description as published by the source.

[!NOTE]
This feature has been disabled by default for all installations from v2.33.8 onwards, including for existent installations. To exploit this vulnerability, the instance administrator must turn on a feature and ignore all the warnings about known vulnerabilities. We're publishing this new advisory to make it clear that all vulnerabilities concerning this feature are disclosed.

For more information about tracking vulnerability issues related to the Command Execution features, check https://github.com/filebrowser/filebrowser/issues/5199.

Summary

The Command Execution feature of File Browser only allows the execution of shell command which have been predefined on a user-specific allowlist. Many tools allow the execution of arbitrary different commands, rendering this limitation void.

Impact

The concrete impact depends on the commands being granted to the attacker, but the large number of standard commands allowing the execution of subcommands makes it likely that every user having the Execute commands permissions can exploit this vulnerability. Everyone who can exploit it will have full code execution rights with the uid of the server process.

Vulnerability Description

Many Linux commands allow the execution of arbitrary different commands. For example, if a user is authorized to run only the find command and nothing else, this restriction can be circumvented by using the -exec flag.

Some common commands having the ability to…

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-2025-52903 has been found in github.com/filebrowser/filebrowser/v2.
Attackers can target a specific entry point like find 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.10 or later.
If unsure, ask your IT team or search "github.com/filebrowser/filebrowser/v2 CVE-2025-52903" on the vendor's site.

CVE-2025-52903 (github.com/filebrowser/filebrowser/v2) — CWE-183 / CVSS v3 8.0
Attack vector: remote (network-reachable) / no user interaction
Attack surface: find / prlimit
Patched: 2.33.10 — 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-183) exists in github.com/filebrowser/filebrowser/v2. Attackers reach the vulnerable code path via find.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/filebrowser/filebrowser/v2. Attack surface: find / prlimit.

🔥 Severity

Severity: High (CVSS 8.0/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 2.33.10.

🛡️ 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

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

  1. 1
    Identify 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 し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/filebrowser/filebrowser/v2 to 2.33.10

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

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

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

Affected packages

go github.com/filebrowser/filebrowser/v2
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.33.10"}]}]

References

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