Seraphinite Accelerator <= 2.29.24 - Unauthenticated Sensitive Information Exposure in Object Cache Directory
Strategic Overview
- Status
- Patched in 2.29.25
- Affected Plugin
- Seraphinite Accelerator
- Affected Version
<= 2.29.24- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2026-90960
At a glance
CVE-2026-90960 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Seraphinite Accelerator WordPress plugin, affecting versions <= 2.29.24. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.29.25; sites on affected versions should update now. Disclosed October 2026, reported by Sawyer.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in Seraphinite Accelerator <= 2.29.24 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Seraphinite Accelerator the fix is 2.29.25: builds <= 2.29.24 are affected, anything from 2.29.25 onward is not.
Remediation
Update to version 2.29.25, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Seraphinite Accelerator 2.29.25 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Seraphinite Accelerator
- 6.4CVE-2024-1568: Seraphinite Accelerator SSRF in OnAdminApi_HtmlCheck
CVE-2024-1568 - 6.1CVE-2026-17532: Seraphinite Accelerator <= 2.29.18 Reflected XSS
CVE-2026-17532 - 6.1CVE-2023-49740: Seraphinite Accelerator <= 2.20.28 Reflected XSS
CVE-2023-49740 - 6.1CVE-2023-5609: Seraphinite Accelerator <= 2.20.28 Reflected XSS
CVE-2023-5609 - 5.4CVE-2023-5610: Seraphinite Accelerator <= 2.20.28 Arbitrary Redirect
CVE-2023-5610 - 4.3CVE-2026-87828: Seraphinite Accelerator <= 2.29.23 Full Admin Area DoS
CVE-2026-87828 - 4.3CVE-2026-3056: Seraphinite… Authenticated (Subscriber+) Log Clearing
CVE-2026-3056 - 4.3CVE-2025-6059: Seraphinite Accelerator CSRF
CVE-2025-6059
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C