Skip to main content
Mallory
CriticalVulnerability

CVE-2025-5746: Arbitrary File Upload in Drag and Drop Multiple File Upload (Pro) - WooCommerce

Published Jul 2, 2025 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS0.74%55th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
IdentifiersCVE-2025-5746CWE-434 · Unrestricted Upload of File with…

CVE-2025-5746 is an arbitrary file upload vulnerability in the Drag and Drop Multiple File Upload (Pro) - WooCommerce plugin for WordPress. The flaw is caused by missing or insufficient file type validation in the dnd_upload_cf7_upload_chunks() function. According to the provided content, the vulnerable upload path is exposed through the WordPress AJAX endpoint /wp-admin/admin-ajax.php using the dnd_upload_cf7_upload_chunks action, and it can be exploited without authentication. The issue affects Drag and Drop Multiple File Upload (Pro) - WooCommerce versions 5.0 through 5.0.5 when bundled with the PrintSpace theme, and the standalone Drag and Drop Multiple File Upload plugin in all versions up to and including 1.7.1. Uploaded files are stored in the wp-content/uploads/ directory. The content further indicates that the plugin's chunked upload mechanism can be abused to split a malicious payload into smaller parts and reassemble it server-side without re-validating the final file, enabling upload of attacker-controlled files such as PHP payloads. Although a .htaccess file is intended to block PHP execution in the upload directory, that protection may not be effective on Nginx, IIS, or misconfigured servers, making remote code execution possible in some deployments.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an unauthenticated attacker to upload arbitrary files to the affected server. Where the web server permits execution of uploaded script content, this can result in remote code execution in the context of the web application, leading to full site compromise, theft or manipulation of WordPress and WooCommerce data, deployment of web shells or malware, persistence, and potential lateral movement from the compromised host. Even where direct code execution is blocked, arbitrary file upload still enables unauthorized storage of attacker-controlled content and may support follow-on attacks depending on server configuration and file handling behavior.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, disable the vulnerable plugin or the affected upload functionality. Restrict access to the vulnerable AJAX action where feasible, and enforce server-side controls that prevent execution of PHP and other script types from upload directories independent of .htaccess, especially on Nginx and IIS. Harden web server configuration to deny execution from wp-content/uploads/, monitor for suspicious POST requests to /wp-admin/admin-ajax.php, and scan the uploads directory for web shells or unexpected executable files. Additional compensating controls include WAF rules to block suspicious multipart or chunked upload requests targeting the vulnerable action and continuous monitoring for newly created files in upload paths.

Remediation

Patch, then assume compromise.

Update the affected plugin to a version that fully validates uploaded file types and securely handles chunk reassembly. Based on the provided content, affected versions are 5.0 through 5.0.5 of the Pro WooCommerce plugin when bundled with the PrintSpace theme, and standalone versions up to and including 1.7.1. If the plugin is bundled with a theme, ensure the bundled component is updated as well rather than assuming the theme package is unaffected. Review the upload handler implementation so that validation is enforced on both individual chunks and the final reconstructed file, using strict allowlisting of extensions and MIME types and rejecting executable content. Remove any malicious or unexpected files already present in wp-content/uploads/ and review logs for exploitation attempts against /wp-admin/admin-ajax.php using the dnd_upload_cf7_upload_chunks action.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2025-5746 exploited in the wild?
Yes. As of Sep 25, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2025-5746?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2025-5746.
Is there a patch for CVE-2025-5746?
Update the affected plugin to a version that fully validates uploaded file types and securely handles chunk reassembly. Based on the provided content, affected versions are 5.0 through 5.0.5 of the Pro WooCommerce plugin when bundled with the PrintSpace theme, and standalone versions up to and including 1.7.1.
How severe is CVE-2025-5746?
CVE-2025-5746 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 0.74% (55th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity4Community discussion across Reddit, Mastodon, and other social sources.