CVE-2026-90960 json
Seraphinite Accelerator <= 2.29.24 - Unauthenticated Sensitive Information Exposure in Object Cache Directory
published 11d ago modified 5d ago also EUVD-2026-114604
- cvss
- 5.3
- 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 25%
- public exploits
- 0
- none known
Summary
The Seraphinite Accelerator plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.29.24 via the WP_Object_Cache::_getFilePath. This makes it possible for unauthenticated attackers to extract complete WordPress user records — including plaintext user_login, user_email, hashed user_pass, and user_activation_key — from predictable gzip-serialized cache files at wp-content/cache/seraphinite-accelerator/oc/g/users/g/<USER_ID>.dat.gz. This vulnerability is only exploitable when the plugin's Object Cache feature is enabled, and requires the attacker to first trigger caching of the target user record (e.g., via an unauthenticated REST API request) before retrieving the resulting cache file.
Is CVE-2026-90960 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
- yes
- Technical impact
- partial
- Assessed
- 5d ago
Exploit prediction
0.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected products
- seraphinitesoft Seraphinite Accelerator
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/71b64440-6a31-40e4-9f38-93eba8858a2c?source=cve
- plugins.trac.wordpress.org /browser/seraphinite-accelerator/tags/2.29.24/cache_obj.php#L257
- plugins.trac.wordpress.org /browser/seraphinite-accelerator/tags/2.29.24/cache_obj.php#L319
- plugins.trac.wordpress.org /browser/seraphinite-accelerator/tags/2.29.24/cache_obj.php#L191
- plugins.trac.wordpress.org /browser/seraphinite-accelerator/tags/2.29.24/common.php#L1873
- plugins.trac.wordpress.org /browser/seraphinite-accelerator/tags/2.29.24/common.php#L2828
- plugins.trac.wordpress.org /browser/seraphinite-accelerator/tags/2.29.24/oper.php#L1595
- plugins.trac.wordpress.org /browser/seraphinite-accelerator/tags/2.29.24/oper.php#L2058
- plugins.trac.wordpress.org /changeset/3701630/seraphinite-accelerator/trunk/cache_obj.php
Sources
- CVE List CVE-2026-90960
- NVD CVE-2026-90960
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.