LiveActive security incident?Get immediate response
CVE Record

CVE-2025-52904: File Browser: Command Execution not Limited to Scope

File Browser provides a file managing interface within a specified directory and it can be used to upload, delete, preview, rename and edit files. In versions of the web application on the 2.x branch, all users have a scope assigned, and they only have access to the files within that scope. The 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. Until this issue is fixed, the maintainers recommend to completely disable `Execute commands` for all accounts. Since 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. 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.

HighCVSS 8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

File Browser versions before 2.33.8 can let enabled command execution ignore the user’s assigned file scope. If an affected instance has this dangerous feature turned on, a privileged attacker could read or change files beyond their intended directory boundary.

Executive priority

Treat as a high-priority configuration and upgrade issue, especially for internet-facing or shared File Browser deployments. The business risk is unauthorized access to files the server can manage, but exploitation depends on the dangerous command feature being enabled.

Technical view

CVE-2025-52904 is a CWE-77 command execution scope-enforcement flaw in filebrowser/filebrowser 2.x versions >=2.0.0 and <2.33.8. The Command Execution feature is not restricted to the user’s configured scope, creating high confidentiality, integrity, and availability impact across server-managed files.

Likely exposure

Exposure is limited to affected File Browser 2.x deployments where Execute commands was enabled. The advisory says exploitation requires the instance administrator to enable the feature despite warnings.

Exploitation context

The bundle does not indicate known active exploitation, and KEV is false. The CVSS vector requires network access and high privileges, with no user interaction. Risk rises if admin or command-enabled accounts are compromised.

Researcher notes

Severity is tempered by AC:H and PR:H, but impact is broad because command execution crosses File Browser scope boundaries. Evidence supports affected versions, default-disable behavior in 2.33.8, and the vendor recommendation to disable Execute commands.

Mitigation direction

  • Upgrade to File Browser v2.33.8 or later where command execution is disabled by default.
  • Disable Execute commands for all accounts until vendor guidance confirms safe use.
  • Review File Browser configuration for any command execution enablement.
  • Follow the GitHub advisory and project issue for remediation updates.

Validation and detection

  • Inventory File Browser instances and confirm versions are not below 2.33.8.
  • Verify Execute commands is disabled for all accounts and groups.
  • Check whether any affected instance was internet-accessible or broadly reachable.
  • Review application and host logs for unexpected command execution activity.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-77: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-52904 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H1.36GitHub_M

Vulnerability scoring details

Base CVSS 3.1 score

8High
CVSS 3.1 vector shape for CVE-2025-52904Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
filebrowserfilebrowser>= 2.0.0, < 2.33.8Listed
Weakness

CWE details

CWE-77

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-77 · source CWE mapping

Improper Neutralization of Special Elements used in a Command ('Command Injection')

Improper Neutralization of Special Elements used in a Command ('Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs