Skip to main content
CVE-2026-90960VulnerabilityPublished

The Seraphinite Accelerator plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-90960· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium.

Data as of 31 Oct 2026, 10:50 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.15.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
seraphinitesoftSeraphinite AcceleratorAffected
  • <=2.29.24
Fixed in–

AI-suggested

Users should consider disabling the Object Cache feature of the Seraphinite Accelerator plugin until a fix is available. Additionally, restricting access to the wp-content/cache/seraphinite-accelerator/oc/g/users/g/ directory via web server configuration can help mitigate unauthorized file retrieval.

Description

The Seraphinite Accelerator WordPress plugin versions up to and including 2.29.24 contain a vulnerability that allows unauthenticated attackers to access sensitive user information. This occurs through predictable gzip-serialized cache files when the plugin's Object Cache feature is enabled. Attackers can extract user data such as usernames, emails, hashed passwords, and activation keys by triggering caching of the target user record and then retrieving the cache file.

References

Community reviews

Loading reviews…