Seraphinite Accelerator <= 2.29.24 - Unauthenticated Sensitive Information Exposure in Object Cache Directory
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- seraphinitesoft Seraphinite Accelerator
through 2.29.24
References 9
plugins.trac.wordpress.org
- browser/seraphinite-accelerator/tags/2.29.24/cache_obj.php#L257
- browser/seraphinite-accelerator/tags/2.29.24/cache_obj.php#L319
- browser/seraphinite-accelerator/tags/2.29.24/cache_obj.php#L191
- browser/seraphinite-accelerator/tags/2.29.24/common.php#L1873
- browser/seraphinite-accelerator/tags/2.29.24/common.php#L2828
- browser/seraphinite-accelerator/tags/2.29.24/oper.php#L1595
- browser/seraphinite-accelerator/tags/2.29.24/oper.php#L2058
- changeset/3701630/seraphinite-accelerator/trunk/cache_obj.php