# CVE-2026-15350: Missing authorization in The Cache Purger

> Authenticated subscribers can delete the plugin's audit log due to missing authorization checks, destroying cache-purge history.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2026
- **Updated:** 16 Jul 2026
- **Also known as:** GHSA-fpxv-63pw-m29m

## What is CVE-2026-15350?

CVE-2026-15350 is a medium-severity missing authorization vulnerability in kevp75 The Cache Purger, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The The Cache Purger plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.3.20. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to permanently truncate the plugin's cache-purge audit log (wp-content/purge.log), destroying the entire cache-purge audit history. The tcp_log_purge nonce is rendered in the admin bar on frontend pages accessible to all authenticated users including subscribers, meaning any authenticated user possesses the nonce required to trigger the deletion.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-15350 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15350 is a medium-severity missing authorization vulnerability in kevp75 The Cache Purger, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-15350 in the wild and no public exploit code.

Affected product: kevp75 The Cache Purger. 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-15350/ (Markdown: https://insights.sbomify.com/CVE-2026-15350/index.md)
```

## Sources

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

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