CVE-2026-93389: LiteSpeed Cache (WordPress plugin) · Information Exposure
Affects LiteSpeed Cache (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 8.2 High.
Data as of 5 Nov 2026, 05:12 UTC
Thin evidence
One scorer or none| CNA (Wordfence) | CVSS 3.1 | 8.2 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 5 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 5 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| litespeedtechLiteSpeed Cache | Affected
| Fixed in– |
AI-suggested
Until a fix is available, it is recommended to disable the Cache REST feature (cache-rest=0) to prevent caching of personalized WooCommerce API responses. Monitor vendor communications for updates and apply official patches once released.
Description
The LiteSpeed Cache plugin for WordPress up to version 7.9.1 has a vulnerability that allows unauthenticated attackers to access sensitive WooCommerce customer data. When Cache REST is enabled (default setting), personalized cart and checkout API responses are cached publicly without varying by user session tokens. This leads to exposure of billing and shipping details, cart contents, and session tokens to unauthorized users.