What’s Vulnerable › Vulnerabilities
CVE-2026-104006: SpeedyCache <= 1.4.2 - Unauthenticated Sensitive Information Exposure via Insecure Cache Configuration via Cache Write Gate Missing comment_author_* Cookie Check
- Severity: low (CVSS 3.7 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.3% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-10-10 · updated 2026-10-13
- Weakness: CWE-524
Description
The SpeedyCache – Cache, Optimization, Performance plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.4.2 via the 'comment_author_*, comment_author_email_*' parameter. This makes it possible for unauthenticated attackers to extract the full name and email address of returning commenters pre-filled into comment form input fields and persisted as the site-wide cached page by any unauthenticated attacker requesting the same public URL. The read-side handler in advanced-cache.php correctly skips cached delivery for requests carrying comment_author_* cookies, but this check is absent on the write path, meaning the cache poisoning is invisible to the victim commenter yet fully exploitable by any unauthenticated attacker with no cookies.
Affected products
- softaculous SpeedyCache – Cache, Optimization, Performance: through 1.4.2
References
- https://plugins.trac.wordpress.org/browser/speedycache/tags/1.4.2/main/advanced-cache.php#L108
- https://plugins.trac.wordpress.org/browser/speedycache/tags/1.4.2/main/cache.php#L151
- https://plugins.trac.wordpress.org/browser/speedycache/tags/1.4.2/main/cache.php#L214
- https://plugins.trac.wordpress.org/browser/speedycache/tags/1.4.2/main/cache.php#L91
- https://plugins.trac.wordpress.org/changeset/3734608/speedycache/trunk/main/cache.php
- https://plugins.trac.wordpress.org/changeset/3734609/speedycache
- https://www.wordfence.com/threat-intel/vulnerabilities/id/c6b8d5ca-34e2-4d25-9185-7fcee790379d?source=cve
Get alerted when CVE-2026-104006 or the next vulnerability affects your stack