Cache Enabler <= 1.8.16 - Unauthenticated Arbitrary File and Directory Deletion
Strategic Overview
- Status
- Patched in 1.8.17
- Affected Plugin
- Cache Enabler
- Affected Version
<= 1.8.16- CVSS
- 9.1Critical
- Weakness type
- CWE-73 · External Control of File Name or Path
- CVE
CVE-2026-19253
At a glance
CVE-2026-19253 is a critical-severity External Control of File Name or Path vulnerability in the Cache Enabler WordPress plugin, affecting versions <= 1.8.16. It carries a CVSS score of 9.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.8.17; sites on affected versions should update now. Disclosed September 2026, reported by Jakub Herman.
Vulnerability Overview
The Cache Enabler plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 1.8.16. This is due to missing path confinement validation in the cache directory resolution logic, allowing URL-supplied path traversal sequences to resolve outside the plugin cache directory. This makes it possible for unauthenticated attackers to delete arbitrary files and directories on the server by supplying a crafted URL containing path traversal sequences to the cache-clearing routine. Another plugin or theme passes a request-derived URL to the cache_enabler_clear_page_cache_by_url hook.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on integrity, availability.
CWE-73: External Control of File Name or Path
The product allows user input to control or influence paths or file names that are used in filesystem operations.
Remediation
Update to version 1.8.17, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Cache Enabler 1.8.17 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Login Security
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C