Cache Enabler · Security record
Is Cache Enabler safe?
No known vulnerability affects the current version (1.8.17). 1 issue was found in earlier versions and fixed, the latest disclosed on Oct 1, 2026.
Checked 5 days ago against the WPVulnerability database, for version 1.8.17.
How it’s looked after
- Last release
- Sep 27, 2026 (1 month ago)
- Releases in the last year
- 2
- Tested up to
- WordPress 7.1.4
- Support resolved
- 0 of 1 threads in two months
- Active installs
- 100K+
1 known vulnerability
- 1 not rated
None affects the current version.
Every known vulnerability in Cache Enabler
Newest first, with any that affect the current version at the top.
Fixed in 1.8.17 · CVE-2026-19253 · Oct 1, 2026 · Patchstack
Questions about Cache Enabler’s security
Is Cache Enabler safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Cache Enabler updated: most attacks target sites that haven’t updated.
Does Cache Enabler have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep Cache Enabler up to date.
Is Cache Enabler still maintained?
Yes. Its last release was 1 month ago. Its authors resolved 0 of the 1 support threads opened in the last two months.
Is Cache Enabler compatible with the latest WordPress?
Yes. It’s tested up to WordPress 7.1.4, the current version.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.