dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-9725

CRITICAL · 9.1 CVSS v3.1 Published 2026-07-03
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 7 weeks old

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 Printcart Web to Print Product Designer for WooCommerce plugin for WordPress is vulnerable to Arbitrary File Deletion in versions up to, and including, 2.5.2 This is due to insufficient path validation in the store_design_data() function, which constructs a filesystem path from the user-supplied 'nbd_item_key' POST parameter sanitized only with sanitize_text_field() — which does not strip path traversal sequences — and then passes that path directly to Nbdesigner_IO::delete_folder() and PHP's rename(). The nonce protecting the nbd_save_customer_design AJAX action is freely obtainable by unauthenticated users via the nbd_check_use_logged_in endpoint. This makes it possible for unauthenticated attackers to delete 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 Printcart Web to Print Product Designer plugin for WooCommerce versions up to 2.5.2 contains an arbitrary file deletion vulnerability. The store_design_data() function uses sanitize_text_field() on the nbd_item_key POST parameter, which fails to block path traversal sequences, allowing attackers to construct paths like ../../ to navigate outside intended directories. The path is then passed directly to Nbdesigner_IO::delete_folder() and PHP's rename(). Since the required nonce is obtainable by unauthenticated users via the nbd_check_use_logged_in endpoint, unauthenticated attackers can delete arbitrary files on the server.

MitigationUpdate the Printcart Web to Print Product Designer plugin to a version beyond 2.5.2 if available, and implement proper path validation with realpath() checking to ensure the resolved path stays within allowed directories. Consider disabling the affected AJAX endpoint or adding proper authentication until the patch is applied.

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
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Verify the Printcart plugin is installed
    Check your WordPress plugins directory for the 'Printcart Web to Print Product Designer' plugin, or query the wp_options table for the active plugin option containing 'printcart'
    Affected if The plugin is installed and active in WordPress
  2. Determine the installed plugin version
    Check the plugin header in printcart.php or query the wp_plugins table for the Version field of the printcart plugin
    Affected if The version is 2.5.2 or lower (any version up to and including 2.5.2)
  3. Check if the AJAX endpoint is accessible without authentication
    Send a POST request to /wp-admin/admin-ajax.php with action=nbd_save_customer_design and observe if the server accepts it without a valid nonce
    Affected if The AJAX endpoint responds without requiring authentication or returns an error related to missing nonce rather than a 403/401 auth failure
  4. Check if the nonce exposure endpoint is accessible
    Send a GET or POST request to /wp-admin/admin-ajax.php with action=nbd_check_use_logged_in and examine the response for a nonce value
    Affected if The endpoint returns a nonce value without requiring authentication
  5. Verify the nbd_item_key parameter is accepted
    Send a POST request to the nbd_save_customer_design endpoint with a crafted nbd_item_key value containing path traversal (e.g., ../../../) and observe if it is processed without validation
    Affected if The parameter is accepted and processed without realpath() validation or path sanitization

If the Printcart Web to Print Product Designer plugin is installed at version 2.5.2 or lower and the AJAX endpoints are accessible without authentication, the environment 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 Printcart Web to Print Product Designer plugin to a version beyond 2.5.2 if available, and implement proper path validation with realpath() checking to ensure the resolved path stays within allowed directories. Consider disabling the affected AJAX endpoint or adding proper authentication until the patch is applied.

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-2026-9725 — 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-2026-9725 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