LiteSpeed Cache ≤ 7.9.1: Your WooCommerce Shoppers' Checkout Details, Served From a Public Cache (CVE-2026-93389, CVSS 8.2)

Running LiteSpeed Cache on your site? Check it against CVE-2024-28000 and CVE-2026-93389 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your LiteSpeed Cache is in one of the affected ranges above, it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

LiteSpeed Cache ≤ 7.9.1: Your WooCommerce Shoppers' Checkout Details, Served From a Public Cache (CVE-2026-93389, CVSS 8.2)

A cache's job is to serve the same page to everyone. That is exactly the problem when the "page" is one shopper's checkout — complete with their name, address, and a live session token. In the LiteSpeed Cache plugin for WordPress, WooCommerce Store API cart and checkout responses can be stored as public cache objects and served to the next, completely unauthenticated visitor. That is CVE-2026-93389, scoring CVSS 8.2, disclosed November 5, 2026 (CNA: Wordfence).

What Happened

CVE-2026-93389 is an exposure of sensitive information to an unauthorized actor (CWE-200) in the LiteSpeed Cache plugin (vendor: LiteSpeed Technologies; wordpress.org slug litespeed-cache, 7,000,000+ active installs at disclosure time).

Am I Affected?

Check wp-admin → Plugins for LiteSpeed Cache and its version. At 7.9.1 or below and running WooCommerce, you are in the affected range. A WordPress site without WooCommerce Store API traffic is not exposed through this path — the precondition is carried here, not buried.

One honesty note, because it is the whole point of how we cover these: our scanner reads this plugin's announced version for both LiteSpeed flaws — the older CVE-2024-28000 (≤ 6.3.0.1) and this one — and a version above the old range says nothing about this one, which is why this CVE has its own dedicated ≤ 7.9.1 branch. Our scanner checks it: run the free mini-scan, or check just this plugin at /tools/plugin-check?slug=litespeed-cache. A version above 7.9.1 earns no "patched" claim from us, though — the CVE record names no fixed version, so the check stays silent above the affected range rather than calling any release the fix.

What To Do Now

  1. Update LiteSpeed Cache to the latest release today. The CVE record names no fixed version, so do not treat any specific release number — from us or anyone else — as a verified "fixed in" claim for this CVE.
  2. Until you have updated, consider disabling Cache REST. The exposed responses are cached because Cache REST is on; it ships on by default, which is why so many stores are in scope without ever having chosen this setting.
  3. Review whether shopper data may already have been served across sessions. Cache logs are the place to look, and any Cart-Token that may have been exposed should be treated as a live session, not a harmless string.
  4. Do not panic-audit the wrong thing. This is a cache-keying flaw, not a malware injection — the fix is the update and the cache configuration, in that order.

The Bigger Lesson

Anything personalized must never enter a shared cache keyed only by URL. Personalization and public caching are opposites, and when both are switched on, the defaults decide which one wins — here, the cache won, and it served one customer's checkout to strangers. When an AI builder (or a performance plugin) adds caching in front of an API that returns per-user data, the review question is never "is it faster?" It is "what varies this cache entry — and is the session one of the things it varies on?" If the honest answer is "nothing varies it," the cache is a broadcast channel.

Related: WordPress Hardening for AI-Built Sites — the standing version of this discipline. How to Check If Your Web App Is Hacked — the follow-up pass if the review finds something you do not recognize.


Running a WooCommerce store on LiteSpeed Cache? Update to the latest release today, then run the free check at preshipit.com/free-scan — our scanner checks it, version-checking this plugin against both LiteSpeed CVEs from the version your site announces to the world.

Check LiteSpeed Cache on your own site — free.

Our free WordPress Plugin Vulnerability Checker pulls LiteSpeed Cache's current version from wordpress.org and lists the vulnerabilities our scanner checks for — CVE-2024-28000 and CVE-2026-93389 included. No scan, no account.

Open the free plugin checker →

The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.

New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.

Running LiteSpeed Cache on your site? Check it against CVE-2024-28000 and CVE-2026-93389 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your LiteSpeed Cache is in one of the affected ranges above, it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report