CVE-2025-1725

Bit File Manager – 100% Free & Open Source File Manager and Code Editor for WordPress <= 6.7 - Authenticated (Subscriber+) Stored Cross-Site Scripting via SVG File Uploads

2025-06-02 20:00
TANG Cheuk Hei (siunam)

Strategic Overview

Status
Patched in 6.8
Affected Plugin
File Manager
Affected Version
<= 6.7
CVSS
6.4Medium
Weakness type
CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE
CVE-2025-1725
View all File Manager vulnerabilities

At a glance

CVE-2025-1725 is a medium-severity Unrestricted Upload of File with Dangerous Type vulnerability in the File Manager WordPress plugin, affecting versions <= 6.7. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 6.8; sites on affected versions should update now. Disclosed June 2025, reported by TANG Cheuk Hei (siunam).

Vulnerability Overview

The Bit File Manager – 100% Free & Open Source File Manager and Code Editor for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG File uploads in all versions up to, and including, 6.7 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses the SVG file.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-434: Unrestricted Upload of File with Dangerous Type

Reaching this weakness in File Manager <= 6.7 takes an account at Subscriber level or above. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.

If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For File Manager the fix is 6.8: builds <= 6.7 are affected, anything from 6.8 onward is not.

Remediation

Update to version 6.8, or a newer patched version

How does WordSec protect against this?

An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: File Manager 6.8 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-1725https://www.wordfence.com/threat-intel/vulnerabilities/id/84ddb481-f989-4ba8-9925-e8327c30de38https://nvd.nist.gov/vuln/detail/CVE-2025-1725

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C