CVE-2026-104006: CWE-524 Use of Cache Containing Sensitive Information in softaculous SpeedyCache – Cache, Optimization, Performance
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.
CVSS v3.1
Score 3.7low
Affected software
softaculous
SpeedyCache – Cache, Optimization, Performance
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-104006 describes a sensitive information exposure vulnerability in the SpeedyCache – Cache, Optimization, Performance WordPress plugin affecting all versions up to and including 1.4.2. The issue involves the caching mechanism improperly storing personalized comment author data (full name and email) in the site-wide cached pages via the 'comment_author_*' parameters. While the read handler correctly avoids serving cached pages when comment_author_* cookies are present, the write handler lacks this check, allowing unauthenticated attackers to poison the cache with sensitive data. This enables attackers to retrieve personal information of returning commenters by requesting the cached URL, without needing authentication or cookies.
Potential Impact
The vulnerability allows unauthenticated attackers to obtain sensitive personal information (full name and email address) of returning commenters by exploiting cache poisoning. This exposure is limited to the cached comment author data and does not affect integrity or availability. The CVSS score of 3.7 (low severity) reflects the limited confidentiality impact and the requirement for specific conditions to exploit.
Mitigation Recommendations
No official patch or fix is currently documented in the provided data. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, administrators should consider disabling the SpeedyCache plugin or restricting access to cached pages containing comment author data. Monitoring vendor advisories for an official update is recommended.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-10-01T16:26:50.185Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6ac9e3622cdf04f6560f781c
Added to database: 10/10/2026, 07:04:02 UTC
Last enriched: 10/10/2026, 07:19:13 UTC
Last updated: 10/10/2026, 21:27:03 UTC
Views: 21
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.