Woocommerce Upload FilesWordPress extension · Vanquish
CVE-2024-10820
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 · uneditedThe WooCommerce Upload Files plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the upload_files() function in all versions up to, and including, 84.3. 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 confidenceThe WooCommerce Upload Files WordPress plugin versions up to 84.3 lacks proper file type validation in its upload_files() function, allowing unauthenticated attackers to upload arbitrary files including executable scripts to the server, potentially achieving remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Woocommerce Upload FilesWordPress extension
< 84.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed plugin versionNavigate to WordPress admin > Plugins > Installed Plugins > WooCommerce Upload Files (by Vanquish) and note the version number displayed. Alternatively, inspect the plugin main file header for the 'Version' tag.Affected if The version is below 84.4 (e.g., 84.3, 84.2, etc.)
-
Confirm plugin is activeIn WordPress admin > Plugins, verify that WooCommerce Upload Files plugin shows as 'Active'. The vulnerability is only exploitable when the plugin is enabled.Affected if The plugin is installed and active on the WordPress site
-
Identify upload functionality exposureCheck if the plugin's upload endpoint is publicly accessible. This typically involves the upload_files() function. Inspect the plugin code for the function at /wp-content/plugins/woocommerce-upload-files/ (path may vary) and verify if any upload form or AJAX endpoint exists without authentication requirements.Affected if The upload_files() function handles requests without requiring authentication or proper file type validation
-
Review recent uploads for suspicious filesExamine the upload directory (commonly wp-content/uploads/ or a plugin-specific subdirectory) for recently added files with executable extensions such as .php, .phtml, .js, .sh, or .exe. Check file creation timestamps.Affected if Unexpected executable files appear in upload directories, especially those created recently and not uploaded by legitimate admin actions
A site is affected if the WooCommerce Upload Files plugin version is below 84.4 and the plugin is active, allowing any visitor to upload arbitrary files including executable scripts via the vulnerable upload_files() function.
Generated from the published advisory. Verify against your own configuration.
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 · scoped84.4
Immediately update the WooCommerce Upload Files plugin to the latest version once available, or disable the plugin if no patch exists. Additionally, review server access logs for suspicious file uploads and remove any malicious files already uploaded.
WooCommerce Upload Files version 84.4
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find the 'WooCommerce Upload Files' plugin
- Click 'Update Now' if an update is available, or manually download version 84.4 or later from the plugin vendor
- After updating, verify the plugin version shows 84.4 or higher in the plugins list
- Test that the file upload functionality works correctly with appropriate file types
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Woocommerce Upload Files
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10820 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-10820 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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