dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-4403

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-09
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 for WooCommerce plugin for WordPress is vulnerable to arbitrary file uploads in all versions up to, and including, 1.1.6 due to accepting a user‐supplied supported_type string and the uploaded filename without enforcing real extension or MIME checks within the upload() function. This makes it possible for unauthenticated attackers 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 Drag and Drop Multiple File Upload for WooCommerce plugin fails to validate file extensions and MIME types in its upload() function, accepting a user-supplied supported_type parameter and filename without verification. This allows unauthenticated attackers to upload arbitrary files including executable code, enabling remote code execution.

MitigationUpdate to version 1.1.7 or later which implements proper file extension and MIME type validation, or disable the plugin until a patch is available.

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. Verify the plugin is installed
    Navigate to WordPress admin dashboard > Plugins and check if 'Drag and Drop Multiple File Upload for WooCommerce' is installed and active
    Affected if The plugin is present and activated in the WordPress environment
  2. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Drag and Drop Multiple File Upload for WooCommerce and note the version number displayed
    Affected if The version is older than the latest patched version that includes proper file extension and MIME type validation
  3. Identify the upload endpoint exposure
    Check for the plugin's upload functionality by reviewing the site's wp-content/plugins directory for the ddbfwu-upload.php or similar upload handling file, then verify if it is accessible without authentication
    Affected if The upload endpoint is publicly accessible without requiring authentication or admin privileges
  4. Confirm the vulnerable upload() function behavior
    Review the plugin's source code in wp-content/plugins/ for the upload() function and verify it accepts supported_type parameters without validating file extensions or MIME types against an allowlist
    Affected if The code accepts arbitrary supported_type parameters and does not validate file extensions or MIME types before processing uploads
  5. Check for unexpected file types in uploads directory
    Inspect the wp-content/uploads/ or configured upload directory for any .php, .exe, .phtml, or other executable file types that should not be present in a standard WooCommerce upload folder
    Affected if Executable or script files are found in the upload directory, indicating potential exploitation

A user is affected if the Drag and Drop Multiple File Upload for WooCommerce plugin is installed and active, with the upload() function accessible without validation on file extensions and MIME types.

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 to version 1.1.7 or later which implements proper file extension and MIME type validation, or disable the plugin until a patch is available.

Recommended fix Moderate confidence

Version 1.1.7 or later (latest available version from wordpress.org)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Drag and Drop Multiple File Upload for WooCommerce'
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/drag-and-drop-multiple-file-upload-for-woocommerce and upload via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the upload functionality still works correctly
  7. 7. Check that the plugin settings for allowed file types are properly configured under the plugin settings page

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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