CVE-2026-93389: LiteSpeed Cache: Unauthenticated disclosure of sensitive WooCommerce customer data

LiteSpeed Cache: Unauthenticated disclosure of sensitive WooCommerce customer data

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.

Description from the National Vulnerability Database, published by Wordfence

What it means for a small business

LiteSpeed Cache is a WordPress plugin. If your website uses it, the flaw is on your site whether or not anyone has noticed yet: attackers scan the whole internet for the plugins with published flaws, usually within days of a record like this one going public.

Most small-business sites run 15 to 40 plugins, and few owners know the list. You can check from WordPress itself (Plugins, then Installed Plugins), or let our free plugin check look it up by name.

How likely is an attack? The Exploit Prediction Scoring System, run by FIRST (the global association of security response teams), puts the odds of this one being exploited in the next 30 days at 0.23%, higher than 13% of CVEs. That’s low, but low isn’t zero, and the odds jump the day someone publishes an exploit. Scored November 7, 2026, updated daily.

Check your own setup

Is LiteSpeed Cache safe? Every recorded flaw in it, the version that fixes each, and whether it’s still maintained.
Website check: reads what your site runs from the outside (WordPress version, plugins it can see, old server software) and matches it against this database.
Server check: what your web server says about itself, and whether that version has known flaws.

Sources

Part of the Huttenlocher Technologies vulnerability database, refreshed twice a day from CISA and the NVD. The title, category and plain-language guidance are ours; check the linked record before acting on a detail. This is general guidance, not a review of your systems.

Weekly security brief

The flaws that hit local websites, every Friday.

One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.