CVE-2026-104006 json
SpeedyCache <= 1.4.2 - Unauthenticated Sensitive Information Exposure via Insecure Cache Configuration via Cache Write Gate Missing comment_author_* Cookie Check
published 30d ago modified 27d ago also EUVD-2026-96208
- cvss
- 3.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 17%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-104006 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 29d ago
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected products
- softaculous SpeedyCache – Cache, Optimization, Performance
Classification
- Weakness
-
- CWE-524 Use of Cache Containing Sensitive Information
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/c6b8d5ca-34e2-4d25-9185-7fcee790379d?source=cve
- plugins.trac.wordpress.org /browser/speedycache/tags/1.4.2/main/cache.php#L151
- plugins.trac.wordpress.org /browser/speedycache/tags/1.4.2/main/cache.php#L91
- plugins.trac.wordpress.org /browser/speedycache/tags/1.4.2/main/cache.php#L214
- plugins.trac.wordpress.org /browser/speedycache/tags/1.4.2/main/advanced-cache.php#L108
- plugins.trac.wordpress.org /changeset/3734609/speedycache
- plugins.trac.wordpress.org /changeset/3734608/speedycache/trunk/main/cache.php
Sources
- CVE List CVE-2026-104006
- NVD CVE-2026-104006
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.