Skip to main content
WordPress plugin recordReviewed

LiteSpeed Cache vulnerability records, and the cache, ESI and purge settings to check

These records are the ones the source data files under the WordPress plugin.

That does not settle what applies to the LiteSpeed web server it talks to. This page shows where the plugin's ESI, REST cache, debug log and purge settings are read.

LiteSpeed Cache vulnerability history

Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 30 records for LiteSpeed Cache. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.

Update to at least version 7.9.2

Worked out from data retrieved on .

Every affected range listed in this source for LiteSpeed Cache ends before version 7.9.2.

A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.

  1. LiteSpeed Cache <= 7.9.1 - Unauthenticated Sensitive Information Disclosure (WooCommerce Store API Cart/Checkout PII + Cart-Token) via Public REST Caching

    Published:
    Last updated:
    Severity:
    High (CVSS 8.2)
    Affected versions
    • All versions up to and including 7.9.1

    Patched versions: 7.9.2

    Update to at least version 7.9.2.

  2. LiteSpeed Cache <= 7.9.1 - Authenticated (Subscriber+) Stored Cross-Site Scripting via VPI Image Attribute Re-Serialization

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.4)
    Affected versions
    • All versions up to and including 7.9.1

    Patched versions: 7.9.2

    Update to at least version 7.9.2.

  3. LiteSpeed Cache <= 7.9.1 - Unauthenticated Stored Cross-Site Scripting via HTML Minifier Predictable Placeholder (md5(REQUEST_TIME) + two-pass str_replace)

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.4)
    Affected versions
    • All versions up to and including 7.9.1

    Patched versions: 7.9.2

    Update to at least version 7.9.2.

  4. LiteSpeed Cache < 7.9.2 - Unauthenticated Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions before 7.9.2

    Patched versions: 7.9.2

    Update to at least version 7.9.2.

  5. LiteSpeed Cache < 7.9.2 - Missing Authorization

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions before 7.9.2

    Patched versions: 7.9.2

    Update to at least version 7.9.2.

Show 25 older records
  1. LiteSpeed Cache < 7.9.2 - Unauthenticated Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions before 7.9.2

    Patched versions: 7.9.2

    Update to at least version 7.9.2.

  2. LiteSpeed Cache <= 7.9 - Unauthenticated Information Exposure

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    Affected versions
    • All versions up to and including 7.9

    Patched versions: 7.9.1

    Update to at least version 7.9.1.

  3. LiteSpeed Cache <= 7.9 - Reflected Cross-Site Scripting via ESI 'esi' Parameter

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.7)
    Affected versions
    • All versions up to and including 7.9

    Patched versions: 7.9.1

    Update to at least version 7.9.1.

  4. LiteSpeed Cache <= 7.9 - Unauthenticated Server-Side Request Forgery

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions up to and including 7.9

    Patched versions: 7.9.1

    Update to at least version 7.9.1.

  5. LiteSpeed Cache <= 7.8.1 - Unauthenticated Stored Cross-Site Scripting via Comment Content

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions up to and including 7.8.1

    Patched versions: 7.9

    Update to at least version 7.9.

  6. LiteSpeed Cache <= 7.7 - Authenticated (Author+) Stored Cross-Site Scripting via img Tag Attributes

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.4)
    Affected versions
    • All versions up to and including 7.7

    Patched versions: 7.8

    Update to at least version 7.8.

  7. LiteSpeed Cache <= 7.7 - Unauthenticated Stored Cross-Site Scripting via QUIC.cloud CCSS/UCSS REST API Endpoints

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions up to and including 7.7

    Patched versions: 7.8

    Update to at least version 7.8.

  8. LiteSpeed Cache <= 7.5.0.1 - Reflected Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    Affected versions
    • All versions up to and including 7.5.0.1

    Patched versions: 7.6

    Update to at least version 7.6.

  9. LiteSpeed Cache <= 7.0.1 - Authenticated (Editor+) Server-Side Request Forgery

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.5)
    Affected versions
    • All versions up to and including 7.0.1

    Patched versions: 7.1

    Update to at least version 7.1.

  10. LiteSpeed Cache <= 6.5.2 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.4)
    Affected versions
    • All versions up to and including 6.5.2

    Patched versions: 6.5.3

    Update to at least version 6.5.3.

  11. LiteSpeed Cache <= 6.5.1 - Unauthenticated Privilege Escalation

    Published:
    Last updated:
    Severity:
    High (CVSS 8.1)
    Affected versions
    • All versions up to and including 6.5.1

    Patched versions: 6.5.2

    Update to at least version 6.5.2.

  12. LiteSpeed Cache <= 6.4.1 - Authenticated (Author+) Path Traversal

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions up to and including 6.4.1

    Patched versions: 6.5.1

    Update to at least version 6.5.1.

  13. LiteSpeed Cache <= 6.5.0.2 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.4)
    Affected versions
    • All versions up to and including 6.5.0.2

    Patched versions: 6.5.1

    Update to at least version 6.5.1.

  14. LiteSpeed Cache <= 6.1 - Unauthenticated Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions up to and including 6.5.0.2

    Patched versions: 6.5.1

    Update to at least version 6.5.1.

  15. litespeed cache <= 6.4.1 - Authenticated (Administrator+) Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.5)
    Affected versions
    • All versions up to and including 6.4.1

    Patched versions: 6.5

    Update to at least version 6.5.

  16. LiteSpeed Cache <= 6.4.1 - Unauthenticated Sensitive Information Exposure via Log Files

    Published:
    Last updated:
    Severity:
    High (CVSS 7.5)
    Affected versions
    • All versions up to and including 6.4.1

    Patched versions: 6.5.0.1

    Update to at least version 6.5.0.1.

  17. LiteSpeed Cache <= 6.3.0.1 - Unauthenticated Privilege Escalation

    Published:
    Last updated:
    Severity:
    Critical (CVSS 9.8)
    Affected versions
    • All versions up to and including 6.3.0.1

    Patched versions: 6.4

    Update to at least version 6.4.

  18. LiteSpeed Cache <= 6.2.0.1 - Cross-Site Request Forgery to Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    Affected versions
    • All versions up to and including 6.2.0.1

    Patched versions: 6.3

    Update to at least version 6.3.

  19. LiteSpeed Cache <= 5.7 - Missing Authorization via update_cdn_status

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    Affected versions
    • All versions up to and including 5.7

    Patched versions: 5.7.0.1

    Update to at least version 5.7.0.1.

  20. LiteSpeed Cache <= 5.7 - Unauthenticated Stored Cross-Site Scripting via 'nameservers' and '_msg'

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions up to and including 5.7

    Patched versions: 5.7.0.1

    Update to at least version 5.7.0.1.

  21. LiteSpeed Cache <= 5.6 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.4)
    Affected versions
    • All versions up to and including 5.6

    Patched versions: 5.7

    Update to at least version 5.7.

  22. LiteSpeed Cache <= 5.3 - Missing Authorization to Toggle Crawler State

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions up to and including 5.3

    Patched versions: 5.3.1

    Update to at least version 5.3.1.

  23. LiteSpeed Cache <= 4.4.3 - Reflected Cross-Site Scripting via qc_res

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    Affected versions
    • From version 1.0.15 up to and including 4.4.3

    Patched versions: 4.4.4

    Update to at least version 4.4.4.

  24. LiteSpeed Cache <= 4.4.3 - Authorization Bypass

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.5)
    Affected versions
    • From version 1.0.15 up to and including 4.4.3

    Patched versions: 4.4.4

    Update to at least version 4.4.4.

  25. LiteSpeed Cache <= 3.6 - Authenticated Stored Cross-Site Scripting via IP setting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.5)
    Affected versions
    • All versions up to and including 3.6

    Patched versions: 3.6.1

    Update to at least version 3.6.1.

Check LiteSpeed Cache on a live site

Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.

LiteSpeed vulnerability records here are filed under the plugin, not the web server

LiteSpeed Cache comes from LiteSpeed Technologies, and its WordPress.org listing splits it in two: General Features, such as minifying CSS, JavaScript and HTML, which may be used with any web server, and LiteSpeed Exclusive Features, such as automatic page caching and caching of WordPress REST API calls, which require OpenLiteSpeed, commercial LiteSpeed products, LiteSpeed-powered hosting or QUIC.cloud CDN.

The records in the history are those the source data files under the slug litespeed-cache. Being filed there does not tell you whether a record also applies to a LiteSpeed web server. The listing's FAQ says the plugin communicates with the LiteSpeed Web Server and its built-in page cache, LSCache, and that the cached pages are stored and managed by LiteSpeed servers.

The listing's installation steps reach the settings from the WordPress Dashboard, under LiteSpeed Cache. WordPress documents an Administrator as having access to all administration features within a single site. Phrases in titles in the history include Comment Content, img Tag Attributes and Shortcode, and the access wording includes Unauthenticated, and Authenticated followed by (Subscriber+), (Contributor+), (Author+), (Editor+) or (Administrator+).

LiteSpeed Cache vulnerabilities on record: ESI, log files and two titles that match

Cross-Site Scripting recurs across the titles, as Stored and as Reflected; others name Privilege Escalation, Missing Authorization, Server-Side Request Forgery and Path Traversal, among other things.

Set an installed version against each record's affected range and patched versions field, because a title can give a different version, as one does here:

  • CVE-2024-28000, whose title ends Unauthenticated Privilege Escalation and whose severity field reads Critical: all versions up to and including 6.3.0.1, with 6.4 in its patched versions field.
  • CVE-2026-76579, whose title ends Reflected Cross-Site Scripting via ESI 'esi' Parameter: all versions up to and including 7.9, with 7.9.1 in its patched versions field.
  • CVE-2024-44000, whose title ends Unauthenticated Sensitive Information Exposure via Log Files: all versions up to and including 6.4.1, with 6.5.0.1 in its patched versions field. The fields say nothing about the versions between the two, so for that record the patched version is the one to reach.
  • CVE-2024-47374 is titled LiteSpeed Cache <= 6.1 - Unauthenticated Stored Cross-Site Scripting, but its affected range is all versions up to and including 6.5.0.2 and its patched versions field reads 6.5.1. The changelog file the plugin ships names this CVE id under its 6.5.1 entry.
  • CVE-2026-113499 and CVE-2026-113500 share one title word for word, LiteSpeed Cache < 7.9.2 - Unauthenticated Stored Cross-Site Scripting, and the same fields: all versions before 7.9.2 affected, 7.9.2 patched. Tell them apart by CVE id.

The LiteSpeed Cache tabs to read on a site you are authorised to review

On a multisite network, the vendor's Multisite page says the Toolbox's Debug Settings, Log View and Beta Test tabs exist only at the network level, and lists Automatically Upgrade, Guest Mode and Purge All On Upgrade among the settings found only there.

Version, and the plugin's own upgrade switch

Write down the LiteSpeed Cache version from the Description column of the WordPress Plugins screen. 1 min read

Cache rules and ESI

The listing gives the path LiteSpeed Cache > Cache. 1 min read

Optimisation features

In the page optimisation section of the plugin's menu, whose tabs on the vendor's page for it include HTML Settings, Media Settings and VPI, record what is ON, including HTML Minify, Lazy Load Images, Localize Resources and Viewport Images. 1 min read

Connected services

On LiteSpeed Cache > General > Online Services, the General page describes an Enable QUIC.cloud services button before a domain is connected and a Disconnect from QUIC.cloud link after. 1 min read

Who can purge, and from where

The Toolbox page lists the purge buttons on Toolbox > Purge and says many also appear in the LiteSpeed menu on the Admin Bar, if they are relevant for the installation. 1 min read

What a version match cannot show about LiteSpeed Cache security

Setting a LiteSpeed Cache version beside the affected ranges in the history shows which records take in that install, not whether a flaw was used against the site.

It also leaves open which addresses sit on the Admin IPs list, whether Debug Log has been recording visitors' requests, and what the cache holds from before the last update. The vendor's Cache page says Purge All on Upgrade determines whether all pages are purged when a plugin, theme or WordPress core is updated: write it down beside the date of the last update.

A WordPress security audit goes further. It starts logged out, lists the REST routes and the admin-ajax actions that plugins register for logged-out visitors, and calls each one without a session.

Frequently asked questions

The affected ranges differ from record to record: CVE-2021-24963, whose title ends Reflected Cross-Site Scripting via qc_res, runs from version 1.0.15 up to and including 4.4.3, and its patched versions field reads 4.4.4. Compare the installed version with every affected range in the history, then read the update guidance at the top of the history alongside the changelog on the plugin's WordPress.org listing.

WordPress displays an update notice on the Plugins screen when a plugin hosted in its directory has a newer version. Read the update guidance at the top of the history beside two vendor sources: the changelog on the WordPress.org listing, which has worded entries as hardening, and LiteSpeed's blog, where it has published posts titled Security Update for LSCWP.

The WordPress.org listing says that when one of the plugin's online image or page optimisation services is requested, data is transmitted to a remote QUIC.cloud server, processed and transmitted back, and that QUIC.cloud keeps copies of that data for up to 7 days and then permanently deletes it. Of those services and the plugin's Reporting feature, it says none collects any visitor data, only server and site data. The same section says QUIC.cloud CDN, if enabled, uses LSCache technology to access the site and serve its content from remote global nodes.

The vendor's Cache page says the My Account, Checkout and Cart pages are excluded from caching by default, and warns that misconfigured page associations in WooCommerce settings may cause pages to be classified incorrectly. To verify, it says to open the page from a browser that is not logged in and look in the developer tools for the X-LiteSpeed-Cache-Control: no-cache header. CVE-2026-93389 has a title ending Unauthenticated Sensitive Information Disclosure (WooCommerce Store API Cart/Checkout PII + Cart-Token) via Public REST Caching: all versions up to and including 7.9.1, with 7.9.2 in its patched versions field. The record names no setting. The vendor's Cache page documents a Cache REST API setting on the Cache tab.

Scope the right test for your application

Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.

Data source and licence

The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.

Copyright 2012-2026 Defiant Inc.

Applies to every record listed below.

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

Copyright 1999-2026 The MITRE Corporation

Applies to every record listed below.

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

Source records