CVE-2026-19253: Cache Enabler < 1.8.17 - Unauthenticated Arbitrary File and Directory Deletion via cache_enabler_clear_page_cache_by_url

Published Oct 1, 2026
·
Updated

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.

Affected Software

1 affected component
KeyCDN Cache Enabler WordPress plugin<1.8.17

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Cache Enabler WordPress plugin to a version that resolves this vulnerability.

    Fixed in 1.8.17

Event History

Oct 1, 2026
CVE Published
via MITRE·06:00 AM
Data Sourced
via MITRE·06:00 AM
DescriptionWeakness
Data Sourced
via NVD·06:17 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which sites are exposed to unauthenticated exploitation?

Exposure requires Cache Enabler before 1.8.17 and either another installed vulnerable Cache Enabler plugin before 1.8.17 or code that passes a request-derived URL to the plugin’s public cache-clearing hook. The issue is not described as affecting every installation by default.

2

What does an attacker need to exploit this issue?

The attacker does not need authentication or user interaction. They need a reachable path in which a request-derived URL is passed to the public cache-clearing hook, allowing the URL-derived filesystem path to be used for deletion.

3

What is the potential impact?

An attacker may delete arbitrary files and directories because the cache purge routine does not validate the URL or restrict deletion to the cache directory. The supplied CVSS vector indicates high integrity and availability impact, with no confidentiality impact.

4

How can I determine whether my site is affected?

Check whether the KeyCDN Cache Enabler WordPress plugin is installed at a version earlier than 1.8.17. Also identify whether another vulnerable Cache Enabler plugin is installed or whether site code passes request-derived URLs to Cache Enabler’s public cache-clearing hook.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203