CVE-2026-19253: Cache Enabler (WordPress plugin) · External Control of File Name or Path
Affects Cache Enabler (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 8.7 High : upgrade to 1.8.17 soon.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.8.17
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade Cache Enabler (WordPress plugin) to 1.8.17.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Cache Enabler | Affected
| Fixed in
|
AI-suggested
A fixed version of the Cache Enabler plugin is available starting from version 1.8.17. Users should upgrade to version 1.8.17 or later to remediate this vulnerability. No other mitigation or temporary fix is indicated. Since this is not a cloud service, site administrators must apply the update manually.
Description
The Cache Enabler WordPress plugin before 1.8.17 does not validate a URL before using it to build a filesystem path in its cache purge routine, and does not confine the resulting deletion to the cache directory, allowing unauthenticated users to delete arbitrary files and directories on sites where another installed Cache Enabler WordPress plugin before 1.8.17 or passes a request-derived URL to its public cache-clearing hook.