# CVE-2026-6403: Quick Playground <= 1.3.3 - Unauthenticated Path Traversal to Arbitrary File Read via 'stylesheet' Parameter

> Unauthenticated attackers can read arbitrary files, including wp-config, via path traversal in the Quick Playground WordPress plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 15 May 2026
- **Updated:** 15 May 2026
- **Also known as:** GHSA-5vxp-83xg-5c9f

## What is CVE-2026-6403?

CVE-2026-6403 is a high-severity path traversal vulnerability in davidfcarr Quick Playground, published on 15 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Quick Playground plugin for WordPress is vulnerable to Path Traversal in versions up to and including 1.3.3. This is due to insufficient path validation in the qckply_zip_theme() function, which appends a user-controlled 'stylesheet' parameter directly to the theme root directory path without sanitizing directory traversal sequences. This makes it possible for unauthenticated attackers to trigger the creation of a ZIP archive containing arbitrary files from the server's filesystem — including wp-config.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-6403?


## How do I fix CVE-2026-6403?

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

## Is CVE-2026-6403 being exploited?

There is no known exploitation of CVE-2026-6403 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6403 and fix it if it is affected.

What it is: CVE-2026-6403 is a high-severity path traversal vulnerability in davidfcarr Quick Playground, published on 15 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6403 in the wild and no public exploit code.

Affected product: davidfcarr Quick Playground. 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-2026-6403/ (Markdown: https://insights.sbomify.com/CVE-2026-6403/index.md)
```

## Sources

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

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