dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-5746

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Drag and Drop Multiple File Upload (Pro) - WooCommerce plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the dnd_upload_cf7_upload_chunks() function in version 5.0 - 5.0.5 (when bundled with the PrintSpace theme) and all versions up to, and including, 1.7.1 (in the standalone version). This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible. The execution of PHP is disabled via a .htaccess file but is still possible in certain server configurations. CVE-2025-49885 may be a duplicate of this.

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 WordPress plugin 'Drag and Drop Multiple File Upload (Pro) - WooCommerce' is vulnerable to arbitrary file uploads due to missing file type validation in the dnd_upload_cf7_upload_chunks() function. This affects versions 5.0-5.0.5 (bundled with PrintSpace theme) and standalone versions up to 1.7.1. Unauthenticated attackers can upload arbitrary files to the server, potentially achieving remote code execution despite a .htaccess protection measure that may fail on certain server configurations.

MitigationUpgrade to the latest version of the plugin to obtain patched file type validation, and review server configuration to ensure .htaccess protections are properly enforced or implement additional server-side upload restrictions.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify plugin installation and version
    Locate the plugin folder 'drag-and-drop-multiple-file-upload-contact-form-7' or 'dnd-upload' in wp-content/plugins/ and open the main PHP file to find the version constant or header
    Affected if The installed version is 5.0 through 5.0.5 (PrintSpace bundle) or 1.7.1 or lower (standalone)
  2. Confirm vulnerable function exists
    Search the plugin files for the string 'dnd_upload_cf7_upload_chunks' - this function handles chunked file uploads and lacks proper file type validation
    Affected if The function dnd_upload_cf7_upload_chunks() is present in the plugin code
  3. Verify upload endpoint is accessible
    Check if the WordPress AJAX endpoint (wp-admin/admin-ajax.php?action=dnd_upload_cf7_upload_chunks or similar) responds without authentication
    Affected if The upload action is reachable without requiring WordPress user authentication
  4. Check .htaccess upload protection
    Inspect the plugin's upload directory (typically /wp-content/uploads/dnd-upload/ or similar) for a .htaccess file that should block executable file types
    Affected if No .htaccess file exists, or the .htaccess does not explicitly deny execution of .php, .phtml, .exe, or other executable extensions in the upload folder

If the plugin version falls within 5.0-5.0.5 or 1.7.1 and earlier, and the upload endpoint is unauthenticated with weak or missing .htaccess restrictions, the environment is likely vulnerable to arbitrary file upload.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to the latest version of the plugin to obtain patched file type validation, and review server configuration to ensure .htaccess protections are properly enforced or implement additional server-side upload restrictions.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $2,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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