dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-6440

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-24
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 WooCommerce Designer Pro plugin for WordPress, used by the Pricom - Printing Company & Design Services WordPress theme, is vulnerable to arbitrary file uploads due to missing file type validation in the 'wcdp_save_canvas_design_ajax' function in all versions up to, and including, 1.9.26. 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 WooCommerce Designer Pro plugin for WordPress (used by the Pricom theme) contains an arbitrary file upload vulnerability in the 'wcdp_save_canvas_design_ajax' function. All versions up to 1.9.26 lack proper file type validation, allowing unauthenticated attackers to upload arbitrary files directly to the server, which can lead to remote code execution.

MitigationUpdate the WooCommerce Designer Pro plugin to version 1.9.27 or later immediately. If no patch is available, disable the plugin/theme and implement file type validation with whitelist approach, plus deploy a WAF rule to block malicious file upload requests.

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. Confirm WooCommerce Designer Pro plugin is installed
    Access WordPress admin dashboard > Plugins, or inspect /wp-content/plugins/ directory for a folder named 'woocommerce-designer-pro', 'wdp', or similar. Check if Pricom theme is active as it bundles this functionality.
    Affected if The plugin or theme bundle named WooCommerce Designer Pro, wcdp, or related to 'designer pro' is present on the WordPress site.
  2. Identify installed plugin version
    If plugin is installed via WordPress admin, view plugin details page to see version number. Alternatively, inspect the main plugin file header in /wp-content/plugins/[plugin-folder]/ for 'Version:' comment, or check any version configuration file present.
    Affected if The version listed is 1.9.26 or lower, or no version can be determined (indicating an old unmaintained installation).
  3. Locate the vulnerable ajax function
    Search the plugin/theme files for the string 'wcdp_save_canvas_design_ajax' using grep, a file search, or WordPress file editor. Examine the function definition to confirm it handles file uploads.
    Affected if The function 'wcdp_save_canvas_design_ajax' exists in the codebase and contains file upload handling logic without apparent file type validation.
  4. Verify ajax endpoint accessibility
    Test if the endpoint /wp-admin/admin-ajax.php?action=wcdp_save_canvas_design_ajax responds to unauthenticated requests (no nonce or login required). Use curl or browser DevTools to send a POST request.
    Affected if The endpoint returns a valid response (not 403 or 401) without requiring authentication, indicating the function is exposed.

If the WooCommerce Designer Pro plugin or bundled theme is present at version 1.9.26 or below AND the wcdp_save_canvas_design_ajax function is exposed without authentication, the site is vulnerable to arbitrary file upload and potential remote code execution.

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 WooCommerce Designer Pro plugin to version 1.9.27 or later immediately. If no patch is available, disable the plugin/theme and implement file type validation with whitelist approach, plus deploy a WAF rule to block malicious file upload requests.

Recommended fix Moderate confidence

Version 1.9.27 or later (latest available version)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the WooCommerce Designer Pro plugin (also known as Pricom - Printing Company & Design Services theme component)
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from the official source (codecanyon.net) and upload it via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is running on a version higher than 1.9.26

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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