dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-10747

HIGH · 7.2 CVSS v3.1 Published 2025-09-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 WP-DownloadManager plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the download-add.php file in all versions up to, and including, 1.68.11. This makes it possible for authenticated attackers, with Administrator-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.

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 WP-DownloadManager plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in download-add.php. Authenticated attackers with Administrator-level access can upload malicious files, potentially achieving remote code execution.

MitigationUpdate the plugin to version 1.68.12 or later which includes proper file type validation. Alternatively, restrict administrator access to trusted users and implement additional web application firewall rules.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 WP-DownloadManager plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'download-manager'
    Affected if The plugin folder exists in the WordPress installation
  2. Check the installed version of WP-DownloadManager
    In WordPress admin, find WP-DownloadManager in the plugins list and note the version number displayed, or open the main plugin file (usually wp-content/plugins/download-manager/wpdm.php) and look for the 'Version:' header in the plugin comments
    Affected if The installed version is lower than 1.68.12
  3. Confirm the vulnerable file exists
    Verify that download-add.php exists in the plugin directory at /wp-content/plugins/download-manager/download-add.php
    Affected if The file download-add.php exists and is readable
  4. Inspect uploaded files for suspicious content
    Check the downloads upload directory (typically /wp-content/uploads/download-manager/ or /wp-content/plugins/download-manager/files/) for file types that should not be present, such as .php, .phtml, .exe, or .js files that could indicate attempted exploitation
    Affected if Executable or script files are present in the downloads directory that were not intentionally uploaded by an administrator
  5. Review administrator user accounts
    In WordPress admin, go to Users > All Users and review accounts with Administrator role for any unrecognized or unexpected accounts
    Affected if There are administrator accounts that should not have access or that were not created by trusted site administrators

You are affected if the WP-DownloadManager plugin is installed with a version earlier than 1.68.12 and the download-add.php file is present and accessible on the site.

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

Update the plugin to version 1.68.12 or later which includes proper file type validation. Alternatively, restrict administrator access to trusted users and implement additional web application firewall rules.

Recommended fix High confidence

1.68.12

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the WP-DownloadManager plugin
  4. Click Update Now or view plugin details to update to the latest version
  5. Verify the update completes successfully to version 1.68.12 or later

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10747 — 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-10747 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