# CVE-2026-93389: LiteSpeed Cache <= 7.9.1 - Unauthenticated Sensitive Information Disclosure (WooCommerce Store API Cart/Checkout PII + Cart-Token) via Public REST Caching

Status: published. Published: 2026-11-05. Updated: 2026-11-05.

The LiteSpeed Cache plugin for WordPress is vulnerable to unauthenticated disclosure of sensitive WooCommerce customer data in all versions up to, and including, 7.9.1 With Cache REST enabled (the shipped default cache-rest=1), LiteSpeed stores WooCommerce Store API GET responses (/wc/store/v1/cart and /wc/store/v1/checkout) as PUBLIC cache objects and does not vary the cache on the Cart-Token or WooCommerce session. A shopper's personalized cart/checkout response is therefore served to any later, cookie-less and token-less client as an LSCache HIT. This makes it possible for unauthenticated attackers to read another shopper's billing and shipping details (name, company, street address, email, phone), cart contents and totals, and the shopper's live Cart-Token session JWT and nonce (enabling cart/checkout-session hijack), plus order_key on the checkout endpoint.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- litespeedtech / LiteSpeed Cache: ≥ 0; ≤ 7.9.1 (affected, semver). Source: CNA: Wordfence

## Severity and prioritization

- CVSS 3.1: 8.2 (high); CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N; source: CNA: Wordfence

- CVSS 3.1: 8.2 (high); CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N; source: NVD: security@wordfence.com

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-200

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/4a66498d-7cf0-4480-b946-94e38f8fd350?source=cve (CNA: Wordfence)

- https://plugins.trac.wordpress.org/changeset/3757253/litespeed-cache/trunk/src/control.cls.php (CNA: Wordfence)

- https://plugins.trac.wordpress.org/changeset/3757253/litespeed-cache/trunk/src/control.cls.php (security@wordfence.com)

- https://www.wordfence.com/threat-intel/vulnerabilities/id/4a66498d-7cf0-4480-b946-94e38f8fd350?source=cve (security@wordfence.com)

## Provenance

- CNA: Wordfence: https://www.cve.org/CVERecord?id=CVE-2026-93389; retrieved 2026-11-05; source updated 2026-11-05

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93389; retrieved 2026-11-05; source updated 2026-11-05

Revision: b09d38e217e132219a04cb5968819b38fc9754df4dfcf731b9f9f097a2733abd

Canonical: https://y2.dev/cve/CVE-2026-93389

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.