CVE-2025-52904: File Browser Command Execution Not Limited To Vulnerability
HIGHCVE-2025-52904 is a HIGH (CVSS 8.0) command execution not limited to vulnerability (CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')) affecting File Browser libraries in the Go ecosystem. The issue involves command execution not limited to scope. Remediation is available by upgrading affected packages to version 2.33.8.
CVE-2025-52904 at a Glance
Security Impact
CVSS: 8.0
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H).
How to Fix CVE-2025-52904
To remediate this vulnerability, upgrade all affected File Browser dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/filebrowser/filebrowser/v2 to 2.33.8
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/filebrowser/filebrowser/v2
How to Check if You Are Affected
To determine whether your application is affected by CVE-2025-52904, inspect your project dependencies for File Browser:
inspect dependencies for github.com/filebrowser/filebrowser/v2
Analyze the terminal output to locate any version of File Browser in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.33.8), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection'), where the product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. In File Browser, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2025-52904 Affected File Browser Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/filebrowser/filebrowser/v2
|
Go |
< 2.33.8
|
2.33.8
|
References
Frequently Asked Questions
What is CVE-2025-52904?
Which File Browser versions are affected?
What version fixes CVE-2025-52904?
Is github.com/filebrowser/filebrowser/v2 affected?
What is the CVSS score of CVE-2025-52904?
What CWE is associated with CVE-2025-52904?
How can I check Go dependencies for CVE-2025-52904?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-hc8f-m8g5-8362",
"modified" : "2026-06-09T11:04:16Z",
"published" : "2025-06-30T17:44:58Z",
"aliases" : [ "CVE-2025-52904" ],
"summary" : "File Browser: Command Execution not Limited to Scope",
"details" : "> [!NOTE]\n> **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.\n>\n> For more information about tracking vulnerability issues related to the Command Execution features, check https://github.com/filebrowser/filebrowser/issues/5199.\n\n## Summary ##\n\nIn the web application, all users have a *scope* assigned, and they only have access to the files within that *scope*.\nThe *Command Execution* feature of Filebrowser allows the execution of shell commands which are not restricted to the scope, potentially giving an attacker read and write access to all files managed by the server.\n\n## Impact ##\n\nShell commands are executed with the *uid* of the server process without any further restrictions.\nThis means, that they will have access to at least\n\n* all files managed by the application from all *scopes*, even those the user does not have access to in the GUI.\n* the Filebrowser database file containing the password hashes of all accounts.\n\nThe concrete impact depends on the commands being granted to the attacker, but due to other vulnerabilities identified (\"Bypass Command Execution Allowlist\", \"Shell Commands Can Spawn Other Commands\", \"Insecure File Permissions\") it is likely, that full read- and write-access will exist.\n\nRead access to the database means, that the attacker is capable of extracting all user password hashes.\nThis enables an offline dictionary attack on the passwords of all accounts, though the choice of the password hash function (*bcrypt* with a complexity of 10) gives a strong protection against such attacks.\nWrite access to the database means that attackers are capable of changing a user's password hash, allowing them to impersonate any user account, including an administrator.\n\n## Vulnerability Description ##\n\nShell commands executed by a user are created as a simple subprocess of the application without any further restrictions.\nThat means, that they have full access to files accessible by the application.\nThe *scope* that is assigned to every account is not considered.\n\nAs a prerequisite, an attacker needs an account with the `Execute Commands` permission and some permitted commands.\n\n## Proof of Concept ##\n\nAny exploit highly depends on the commands granted to the attacker.\nThe following screenshot shows, how all password hashes can be extracted using only the `grep` command:\n\n\n\n## Recommended Countermeasures ##\n\nUntil this issue is fixed, we recommend to completely disable `Execute commands` for all accounts.\nSince the command execution is an inherently dangerous feature that is not used by all deployments, it should be possible to completely disable it in the application's configuration.\nAs a defense-in-depth measure, organizations not requiring command execution should operate the Filebrowser from a *distroless* container image.\n\nThere are two approaches to fixing this issue:\n\n1. Limiting the process when it is started e.g., by using *user namespaces* with a tool like *Bubblewrap*. If this path is chosen, it is important to use a method that works both on a bare-metal server and within an unprivileged container.\n2. Re-architecting the command execution feature so that file in the various *scopes* have a distinct *uid* as an owner and all shell command are executed under the *uid* of the user's *scope*.\n\n## Timeline ##\n\n* `2025-03-26` Identified the vulnerability in version 2.32.0\n* `2025-04-11` Contacted the project\n* `2025-04-18` Vulnerability disclosed to the project\n* `2025-06-25` Uploaded advisories to the project's GitHub repository\n* `2025-06-25` CVE ID assigned by GitHub\n* `2025-06-25` A patch version has been pushed to disable the feature for all existent installations, and making it **opt-in**. A warning has been added to the documentation and is printed on the console if the feature is enabled. Due to the project being in maintenance-only mode, the bug has not been fixed. Fix is tracked on https://github.com/filebrowser/filebrowser/issues/5199.\n\n## References ##\n\n* [Sandboxing Applications with Bubblewrap: Securing a Basic Shell](https://sloonz.github.io/posts/sandboxing-1/)\n* [\"Distroless\" Container Images.](https://github.com/GoogleContainerTools/distroless)\n* [Original Advisory](https://github.com/sbaresearch/advisories/tree/public/2025/SBA-ADV-20250326-01_Filebrowser_Command_Execution_Not_Limited_To_Scope)\n\n## Credits ##\n\n* Mathias Tausig ([SBA Research](https://www.sba-research.org/))",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/filebrowser/filebrowser/v2"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "2.33.8"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/filebrowser/filebrowser/security/advisories/GHSA-hc8f-m8g5-8362"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-52904"
}, {
"type" : "WEB",
"url" : "https://github.com/filebrowser/filebrowser/issues/5199"
}, {
"type" : "WEB",
"url" : "https://github.com/GoogleContainerTools/distroless"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/filebrowser/filebrowser"
}, {
"type" : "WEB",
"url" : "https://github.com/sbaresearch/advisories/tree/public/2025/SBA-ADV-20250326-01_Filebrowser_Command_Execution_Not_Limited_To_Scope"
}, {
"type" : "WEB",
"url" : "https://pkg.go.dev/vuln/GO-2025-3793"
}, {
"type" : "WEB",
"url" : "https://sloonz.github.io/posts/sandboxing-1"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-77" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2025-06-30T17:44:58Z",
"nvd_published_at" : "2025-06-26T19:15:21Z"
}
}