# CVE-2025-10268: Path traversal in Printcart Web to Print Product Designer for WooCommerce

> Unauthenticated attackers can exploit path traversal to retrieve directory listings from arbitrary server locations via the Printcart WooCommerce plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-mm7w-7c83-99xv

## What is CVE-2025-10268?

CVE-2025-10268 is a medium-severity path traversal vulnerability in Unknown Printcart Web to Print Product Designer for WooCommerce, published on 26 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2025-10268?


## How do I fix CVE-2025-10268?

No fix has been published for CVE-2025-10268 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-10268 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10268 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10268 and fix it if it is affected.

What it is: CVE-2025-10268 is a medium-severity path traversal vulnerability in Unknown Printcart Web to Print Product Designer for WooCommerce, published on 26 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10268 exists.

Affected product: Unknown Printcart Web to Print Product Designer for WooCommerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-10268/ (Markdown: https://insights.sbomify.com/CVE-2025-10268/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-10268
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-10268
- OSV: https://osv.dev/vulnerability/CVE-2025-10268

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-10268/
Summaries are generated and may contain mistakes; the official description above is the record.