dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-60219

CRITICAL · 10.0 CVSS v3.1 Published 2025-09-26
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
Unrestricted Upload of File with Dangerous Type vulnerability in HaruTheme WooCommerce Designer Pro wc-designer-pro allows Upload a Web Shell to a Web Server.This issue affects WooCommerce Designer Pro: from n/a through <= 1.9.24.

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 · moderate confidence

The WooCommerce Designer Pro plugin contains an unrestricted file upload vulnerability that allows unauthenticated attackers to upload dangerous file types (including web shells) directly to the web server. This critical flaw enables remote code execution by circumventing file type validation and upload restrictions.

MitigationImmediately restrict or disable the file upload functionality until a patched version is available from the vendor. If possible, move any existing uploaded files outside the web root and review the server for any suspicious uploaded files.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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. Identify if WooCommerce Designer Pro is installed
    Check your WordPress site's wp-content/plugins/ directory for a folder named 'designer-pro' or 'woocommerce-designer-pro', or use the WordPress admin Plugins page to list installed plugins
    Affected if The plugin is present on the system
  2. Determine the installed plugin version
    If the plugin is installed, locate the main PHP file (usually designer-pro.php or similar) and check the Version header in the plugin comment block, or view the version in the WordPress plugin admin panel
    Affected if The installed version falls within the vulnerable version range and no patch has been applied
  3. Inspect the uploads directory for unexpected file types
    Examine the wp-content/uploads/ directory (or custom upload path) for files with extensions such as .php, .phtml, .phar, .php5, .php7, .js, .asp, .exe, .sh, .cgi, or other executable extensions that should not be present
    Affected if Any suspicious or unexpected executable files are found in upload directories, especially in folders accessible via web
  4. Review access logs for unauthenticated file upload requests
    Check your web server access logs (Apache, Nginx) for POST requests to typical upload endpoints (often includes 'upload', 'file', 'image' in the URL) that originate from unauthenticated sources and contain file uploads
    Affected if There are POST requests to upload endpoints from unauthenticated IP addresses, particularly those uploading files with dangerous extensions
  5. Verify file upload restrictions are in place
    Check the plugin settings in the WordPress admin panel under the Designer Pro settings for any file upload functionality, and verify if allowed file type restrictions are properly configured and enforced
    Affected if The plugin allows unrestricted file uploads without proper validation or accepts dangerous file types

A user is affected if the WooCommerce Designer Pro plugin is installed, the uploads directory contains suspicious executable files, or unauthenticated upload requests appear in server logs.

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

Immediately restrict or disable the file upload functionality until a patched version is available from the vendor. If possible, move any existing uploaded files outside the web root and review the server for any suspicious uploaded files.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,470
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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