dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-1725

MEDIUM · 6.4 CVSS v3.1 Published 2025-06-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Bit File Manager WordPress plugin up to version 6.7 fails to sanitize SVG file uploads, allowing authenticated attackers with Subscriber-level access or higher to upload SVG files containing malicious JavaScript payloads. Since SVG files are XML-based, embedded scripts execute when users access the uploaded files, leading to stored XSS.

MitigationUpgrade to version 6.8 or later which implements proper SVG sanitization. Until patched, consider disabling SVG uploads or restricting file management capabilities to trusted users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Bit File Manager plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Bit File Manager' in the list
    Affected if Plugin is present and active in the WordPress installation
  2. Check installed plugin version
    Click on the plugin in the Plugins list to view details, or check the plugin header in wp-content/plugins/bit-file-manager/index.php for the 'Version' constant
    Affected if Version is 6.7 or lower (the vulnerable range)
  3. Confirm SVG upload capability is enabled
    Navigate to Bit File Manager settings (usually under Settings > File Manager or the plugin's own menu). Look for file type allowlists or upload restrictions. Check if '.svg' or 'SVG' is listed among allowed upload extensions
    Affected if SVG file extension is explicitly allowed in the upload allowlist or no file type restrictions are configured
  4. Verify subscriber-level users have file manager access
    In WordPress, go to Users > Roles or the Bit File Manager role settings. Check if the 'Subscriber' role (or any low-privileged role) has 'file_manager' capability or access to the file manager interface
    Affected if Subscriber role or roles without administrative privileges have been granted file management capabilities
  5. Inspect recently uploaded SVG files
    Use the file manager to browse uploaded directories (commonly /wp-content/uploads/ or within the file manager root). Look for .svg files, particularly those with unusual filenames or recent upload timestamps
    Affected if SVG files exist in any accessible directory, especially if uploaded by low-privileged users

A user is affected if the Bit File Manager plugin (versions 6.7 or below) is installed with SVG uploads enabled and low-privileged users (Subscriber+) have file manager access, allowing potential stored XSS via malicious SVG files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 6.8 or later which implements proper SVG sanitization. Until patched, consider disabling SVG uploads or restricting file management capabilities to trusted users only.

Recommended fix High confidence

Upgrade to Bit File Manager version 6.8 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Bit File Manager' plugin
  4. Check if an update is available (should show version 6.8 or later)
  5. If update available, click 'Update Now' to upgrade to the fixed version
  6. If no automatic update appears, manually download version 6.8+ from wordpress.org/plugins/bit-file-manager/ and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the version number reflects the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1725 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1725 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data