The LiteSpeed Cache plugin for WordPress is vulnerable to unauthenticated disclosure of sensitive WooCommerce customer
Source GCVE Database
Not known to be exploited · CVSS 8.2 High.
Data as of 5 Nov 2026, 07:26 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) if possible to prevent public caching of personalized WooCommerce API responses.
Description
The LiteSpeed Cache plugin for WordPress versions up to and including 7.9.1 has a vulnerability that allows unauthenticated attackers to access sensitive WooCommerce customer data. When the Cache REST feature is enabled (default setting), personalized WooCommerce Store API GET responses are cached publicly without varying by session tokens. This flaw enables attackers to retrieve other shoppers' billing and shipping information, cart contents, and session tokens, potentially hijacking live cart sessions.