Back to Article List

LiteSpeed Cache Leaked WooCommerce Cart Data: CVE-2026-93389

LiteSpeed Cache Leaked WooCommerce Cart Data: CVE-2026-93389 - LiteSpeed Cache Leaked WooCommerce Cart Data: CVE-2026-93389

If you run a WooCommerce store on LiteSpeed Cache, update the plugin to a patched version right now, then check whether your cache served customer cart data to people who were never logged in. The bug (CVE-2026-93389) let LiteSpeed cache responses from the WooCommerce Store API — the endpoints that power the cart and checkout — and hand the same cached copy to the next visitor. That copy could contain names, email addresses, shipping details and the cart token.

The short version: one shopper's checkout data could land in a stranger's browser. For an EU shop, that is personal data disclosed to an unauthorised party, which drags GDPR breach rules into the conversation.

This post is a response plan, not a panic. Update first, then work out whether anything actually leaked, then decide if you owe anyone a notification.

What actually went wrong

LiteSpeed Cache was caching unauthenticated requests to the WooCommerce Store API and reusing them across visitors, so personal data baked into one response got served to the next person who hit the same URL.

The Store API (the /wp-json/wc/store/ routes) drives the modern block-based cart and checkout. Those responses are meant to be per-session and never cached — they carry cart contents, applied shipping and billing fields, and a cart token that identifies the session. When a full-page or REST cache treats those responses like static content, it can store one customer's data and replay it for everyone who requests the same endpoint.

No login required to trigger it. An attacker didn't need an account, a password, or anything clever — just a request to a cacheable endpoint at the right moment to collect whatever the cache was holding. That is what "unauthenticated sensitive information disclosure" means in the advisory: the door was open to anyone.

How to tell if your store was exposed

Check your LiteSpeed version first, then look for cache headers on Store API responses — if those endpoints were being cached, you were at risk.

Start with the version. In WordPress Admin → Plugins, confirm LiteSpeed Cache is on the patched release (above the vulnerable 7.9.x line referenced in the advisory). If you're behind, update before you do anything else, then purge the entire cache from LiteSpeed Cache → Toolbox → Purge All.

Now test the endpoints directly. From a terminal, send an unauthenticated request and read the headers:

  • curl -I https://yourstore.com/wp-json/wc/store/v1/cart — look at the response headers.
  • If you see x-litespeed-cache: hit on that route, it was being served from cache. That's the red flag.
  • A healthy config returns no cache hit on Store API routes, or shows them explicitly excluded.

Also scan your access logs for repeated unauthenticated hits to /wp-json/wc/store/ endpoints, especially bursts from a single IP or user agent. On TPC Hosting you can pull raw access logs from the control panel; grep for store/v1/cart and store/v1/checkout and note anything that looks like scraping rather than normal shopping. Evidence of actual data served to a third party is what separates "theoretical exposure" from "reportable breach," and your logs are where that evidence lives.

The GDPR side for EU shops

If customer personal data was genuinely served to an unauthorised person, that is a personal data breach under GDPR, and you generally have 72 hours from becoming aware to notify your supervisory authority — unless the breach is unlikely to risk people's rights.

The data in play here matters. Names, email addresses and shipping details are clearly personal data. A cart token is a session identifier that can be tied to a person's activity. If your logs show those details were actually handed to a third party, you're past "a vulnerability existed" and into "a breach occurred."

Two separate obligations, and people mix them up:

  • Notify your supervisory authority (Article 33) within 72 hours of becoming aware, if the breach is likely to result in a risk to individuals. Document your reasoning either way.
  • Tell affected customers (Article 34) only if the breach is likely to result in a high risk to them.

Keep an internal record regardless. Even where you decide no notification is required, GDPR expects you to log what happened, what data was involved, and why you concluded the risk was low. A short written assessment — dated, with your log findings attached — is your defence if a regulator ever asks. If you can show from logs that the Store API was excluded from caching and nothing was ever served, that's a strong "no actual exposure" position.

How to cache WooCommerce without leaking the cart

Cache your static and page content aggressively, but never cache cart, checkout, my-account, or the Store API — those must always serve fresh, per-session responses.

LiteSpeed Cache excludes the classic WooCommerce pages by default, but block-based checkout and the Store API REST routes are exactly where configs go wrong. Lock these down explicitly:

  • Exclude the dynamic pages: in LiteSpeed Cache → Cache → Excludes, confirm cart, checkout, and my-account are listed as "Do Not Cache URIs."
  • Exclude the Store API: add /wp-json/wc/store/ to the Do Not Cache URIs so those REST responses are never stored.
  • Don't cache REST blindly: if you've enabled any "cache REST API" option, make sure WooCommerce Store routes are carved out.
  • Respect cache-control: leave LiteSpeed set to honour the no-cache headers that WooCommerce sends on session responses.
  • Vary by cookie where needed: ensure logged-in and cart-holding sessions aren't served the public cached copy.

After changing any of this, purge everything and re-run the curl test above. You want x-litespeed-cache: hit on your homepage and product pages, and no cache involvement on cart, checkout or Store API routes. That's the whole game: fast where it's safe, fresh where it's personal.

One habit worth keeping — audit your cache exclusions after every major plugin update. Caching plugins and WooCommerce both ship changes to how dynamic routes are handled, and a config that was safe last year can quietly start caching something new.

A clean response checklist

Work through these in order; each step either closes the risk or tells you how serious it was.

StepWhat to doWhy
1. PatchUpdate LiteSpeed Cache to the fixed versionStops the leak at the source
2. PurgePurge All cacheClears any already-cached personal data
3. ExcludeAdd /wp-json/wc/store/ and cart/checkout to Do Not CachePrevents recurrence
4. Testcurl -I the Store API routes, check for cache hitsConfirms the fix
5. InvestigateGrep access logs for scraping of Store API endpointsEstablishes if data was actually served
6. AssessWrite a dated breach assessmentGDPR accountability, notify if needed

If any step leaves you unsure — especially reading logs or deciding whether something is reportable — our support team can help you pull the raw logs and sanity-check your cache config. With TPC Hosting you get AI on chat at any hour and real engineers following up in business hours, and because our hosting is EU-based and GDPR-friendly, your data and your logs stay where they should.

The quiet lesson

Caching is the one layer where "faster" and "safer" pull in opposite directions, so the WooCommerce dynamic routes need a permanent exclusion list, not a one-time fix.

This wasn't a WooCommerce flaw or a LiteSpeed flaw so much as a collision: a cache that got too eager about REST responses it should have left alone. Any full-page or edge cache can make the same mistake. The defence is boring and reliable — know exactly which routes carry personal data, exclude them explicitly, and re-check after updates.

If you've patched, purged, excluded the Store API, and your logs are clean, you're in good shape. Write up what you found, keep it on file, and move on with a cache config you can actually trust.

Need a hand checking your setup or moving to hosting that makes this easier? Come talk to us at tpc-hosting.com — free migration included, and 30 days to back out if it's not for you.

FAQ

Does CVE-2026-93389 affect my store if I don't use block checkout?

It can still affect you, because the risk is tied to the WooCommerce Store API being cached, not just the block checkout UI. Even sites using classic checkout may expose the /wp-json/wc/store/ REST routes, so test those endpoints and add the exclusion regardless of which checkout you run.

How do I know if real customer data actually leaked, not just that it could have?

Check your raw access logs for repeated unauthenticated requests to the Store API cart and checkout endpoints. Normal shopping produces scattered hits tied to real sessions; a pattern of rapid requests from one IP or bot suggests someone was collecting cached responses, which is the difference between theoretical exposure and an actual breach.

Do I have to report this to a GDPR regulator?

Only if personal data was actually served to an unauthorised person and the breach is likely to risk individuals' rights, in which case you have 72 hours to notify your supervisory authority. If your logs show the Store API was never cached or nothing was served, document that conclusion and keep it on file rather than notifying.

Will excluding cart and checkout from cache slow my store down?

No, because those pages are meant to be personal and were never good candidates for caching anyway. Your homepage, product pages and category listings still cache normally, so the vast majority of your traffic stays fast while only the per-session routes serve fresh.

What cache headers should I expect after fixing this?

Static and product pages should show x-litespeed-cache: hit, while cart, checkout, my-account and /wp-json/wc/store/ routes should show no cache hit at all. Run curl -I against those URLs after purging to confirm the dynamic routes are being served fresh every time.