dbcve.org
VulnerabilityAwaiting classification

CVE-2025-10268

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 Printcart Web to Print Product Designer for WooCommerce WordPress plugin through 2.4.8 is vulnerable to path traversal which makes it possible for the attacker to retrieve the directory listing for arbitrary directories on the server.

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 WordPress versions up to 2.4.8 contains a path traversal vulnerability that allows unauthenticated attackers to retrieve directory listings from arbitrary directories on the server by manipulating path parameters.

MitigationUpdate the Printcart plugin to the latest version when available, and implement strict input validation with allowlist-based path restrictions to prevent directory traversal sequences.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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 Printcart plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'printcart' or similar variant of the Printcart Web to Print Product Designer plugin
    Affected if The plugin directory exists on the server
  2. Identify the installed plugin version
    Open the main plugin PHP file (typically the primary PHP file in the plugin folder) and locate the 'Version:' header in the plugin comment block, or check the WordPress admin Plugins page for the Printcart plugin version
    Affected if The installed version is 2.4.8 or any earlier version (versions prior to the fix)
  3. Verify the plugin is active
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or query the WordPress database (wp_options table) for the active_plugins option to confirm Printcart is enabled
    Affected if The plugin is actively enabled on the WordPress site
  4. Test for vulnerable path parameter exposure
    Send an HTTP GET request to the Printcart plugin endpoints (common paths include /?page=printcart, /printcart/, or AJAX endpoints) with path traversal sequences such as ../ or absolute paths like /etc/ in parameters named 'path', 'folder', 'dir', or similar
    Affected if The server responds with directory listings or file contents from paths outside the intended directory

A user is affected if the Printcart plugin versions 2.4.8 or below are installed and active, and the path traversal vulnerability in the plugin endpoints is exploitable via HTTP requests with manipulated path parameters.

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 Printcart plugin to the latest version when available, and implement strict input validation with allowlist-based path restrictions to prevent directory traversal sequences.

Recommended fix Moderate confidence

latest version newer than 2.4.8 (check WordPress plugin repository for current stable release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Printcart Web to Print Product Designer for WooCommerce' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Verify the update completed successfully
  6. 6. Test that the product designer functionality works correctly after the update

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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