# CVE-2026-2500: Quick Playground <= 1.3.4 - Authenticated (Administrator+) Arbitrary File Read via 'filename' Parameter

> Authenticated administrators can read arbitrary server files via path traversal in the Quick Playground WordPress plugin when synced with Playground.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jun 2026
- **Updated:** 6 Jun 2026
- **Also known as:** GHSA-59q7-qrf3-gfx3

## What is CVE-2026-2500?

CVE-2026-2500 is a medium-severity path traversal vulnerability in davidfcarr Quick Playground, published on 6 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Quick Playground plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 1.3.4. This is due to the `qckply_data()` function passing the user-supplied `filename` POST parameter directly to `file_get_contents()` without any validation, sanitization, or path restriction. This makes it possible for authenticated attackers, with Administrator-level access and above, to read arbitrary files on the server, such as `wp-config.php` or `/etc/passwd`, which can contain sensitive information. Note: This vulnerability is only exploitable when the site has been synced with WordPress Playground (the `is_qckply_clone` option is set) or when running on `playground.wordpress.net`.

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

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


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

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

## Is CVE-2026-2500 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2500 is a medium-severity path traversal vulnerability in davidfcarr Quick Playground, published on 6 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2500 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-2500/ (Markdown: https://insights.sbomify.com/CVE-2026-2500/index.md)
```

## Sources

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

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