HomeWordPress vulnerabilitiesSpeedyCache
SpeedyCache vulnerabilities
SpeedyCache has 2 known vulnerabilities in this database. The most recent published record is dated 28 Jul 2026.
- Known vulnerabilities
- 2
- Active installs
- 600,000+
- Latest version
- 1.4.2
- Last updated
- 23 Sep 2026
- Most recent
- 28 Jul 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Arbitrary file read CVE-2026-5114 | Medium 4.9 | Up to 1.3.8 | Fixed in a later version (latest 1.4.2) | 28 Jul 2026 |
| Broken access control CVE-2023-6598 | Medium 4.3 | Up to 1.1.3 | Fixed in a later version (latest 1.4.2) | 11 Jan 2024 |
Read the published descriptions
- CVE-2026-5114, 28 Jul 2026
- The SpeedyCache plugin for WordPress is vulnerable to Arbitrary File Read via Path Traversal in all versions up to, and including, 1.3.8. This is due to a mismatch between CSS URL validation (which allows query strings like `.css?...`) and path resolution (which strips query strings), combined with no validation that the resolved file is actually a CSS file. This makes it possible for authenticated attackers, with Administrator-level access and above, to read arbitrary files from the server (including `wp-config.php` and `/etc/passwd`) by injecting crafted `<link>` tags into page content, with the file contents written to publicly accessible cache files. CVE record
- CVE-2023-6598, 11 Jan 2024
- The SpeedyCache plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the speedycache_save_varniship, speedycache_img_update_settings, speedycache_preloading_add_settings, and speedycache_preloading_delete_resource functions in all versions up to, and including, 1.1.3. This makes it possible for authenticated attackers, with subscriber-level access and above, to update plugin options. CVE record
What to do if you run SpeedyCache
If you run SpeedyCache, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new SpeedyCache vulnerabilities
Free. We email you when a new vulnerability is published for SpeedyCache, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.