Subscriber-level audit-log deletion via exposed nonce
Published Jul 16, 2026 · Updated Jul 16, 2026
Authorization bypass in The Cache Purger 2.3.20 and earlier allows remote authenticated users to erase the cache-purge audit log. The frontend admin bar renders the tcp_log_purge nonce to subscribers, and the the_log_purge request path accepts it without a capability check before truncating wp-content/purge.log. Subscriber-level access is sufficient, and exploitation permanently destroys the plugin's cache-purge audit history without altering cached content.
Summary
What happened
Authorization bypass in The Cache Purger 2.3.20 and earlier allows remote authenticated users to erase the cache-purge audit log. The frontend admin bar renders the tcp_log_purge nonce to subscribers, and the the_log_purge request path accepts it without a capability check before truncating wp-content/purge.log. Subscriber-level access is sufficient, and exploitation permanently destroys the plugin's cache-purge audit history without altering cached content.
The record
- CVE
- CVE-2026-15350
- Published
- Jul 16, 2026
- Updated
- Jul 16, 2026
- Vendor
- Kevin Pirnie
- Product
- The Cache Purger
- Classifications
- CWE-862, T1070
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 16, 2026CVE publishedPublication date reported by the CVE source.
- Jul 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.3.20
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo