dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-6439

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-11
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 deletion due to insufficient file path 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 delete all files in an arbitrary directory on the server, which can lead to remote code execution, data loss, or site unavailability.

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 WordPress plugin is vulnerable to arbitrary file deletion due to insufficient input sanitization in the wcdp_save_canvas_design_ajax function. Unauthenticated attackers can manipulate file paths to delete any file on the server, potentially leading to remote code execution through deletion of security files, complete site compromise, or denial of service.

MitigationUpdate the WooCommerce Designer Pro plugin to version 1.9.27 or later immediately. If the update is unavailable, deactivate and remove the plugin. If files have already been deleted, restore from a clean backup and audit the server for additional compromise.

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. Locate the WooCommerce Designer Pro plugin installation
    Check the WordPress plugins directory at /wp-content/plugins/ for a folder named 'woocommerce-designer-pro' or similar (may also be 'wdp' or 'designer-pro'). Look for the main plugin PHP file and check the plugin header for the version number.
    Affected if The plugin folder exists and the version is below 1.9.27 (or the version cannot be determined).
  2. Identify the installed plugin version
    Open the main plugin file (usually named wcdp.php, index.php, or similar in the plugin folder) and locate the 'Version' field in the plugin header comment at the top of the file.
    Affected if The version number retrieved is lower than 1.9.27.
  3. Verify the vulnerable AJAX endpoint exists
    Check the plugin source code for the function 'wcdp_save_canvas_design_ajax' and confirm it is hooked to WordPress AJAX actions (wp_ajax_wcdp_save_canvas_design_ajax or wp_ajax_nopriv_wcdp_save_canvas_design_ajax). The nopriv hook indicates unauthenticated access is possible.
    Affected if The function exists and is hooked to wp_ajax_nopriv_ (unauthenticated AJAX), meaning the endpoint is accessible to anyone.
  4. Confirm file deletion capability in the vulnerable function
    Review the wcdp_save_canvas_design_ajax function code to verify it accepts a file path parameter and performs an unlink or delete operation without proper sanitization or validation.
    Affected if The function accepts user-supplied paths and deletes files without validating they belong to the plugin's intended upload/design directory.

If WooCommerce Designer Pro is installed with a version below 1.9.27 and the vulnerable AJAX endpoint is accessible without authentication, the site is affected by this arbitrary file deletion vulnerability.

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

Update the WooCommerce Designer Pro plugin to version 1.9.27 or later immediately. If the update is unavailable, deactivate and remove the plugin. If files have already been deleted, restore from a clean backup and audit the server for additional compromise.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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