Is LiteSpeed Cache safe?

No known vulnerability affects the current version (7.9.3). 30 issues were found in earlier versions and fixed, the latest disclosed on Oct 28, 2026.

Checked 5 days ago against the WPVulnerability database, for version 7.9.3.

How it’s looked after

Last release: Nov 3, 2026 (4 days ago)
Releases in the last year: 8
Tested up to: WordPress 7.1.4
Support resolved: 37 of 76 threads in two months
Active installs: 7M+

30 known vulnerabilities

2 critical
8 high
16 medium
4 not rated

None affects the current version.

Disclosed each year

20202
20212
20232
202411
20252
202611

Every known vulnerability in LiteSpeed Cache

Newest first, with any that affect the current version at the top.

medium
Authenticated (Subscriber+) Stored Cross-Site Scripting via VPI Image Attribute Re-Serialization
Fixed in 7.9.2 · CVE-2026-109215 · Oct 28, 2026 · Wordfence
medium
Unauthenticated Stored Cross-Site Scripting via HTML Minifier Predictable Placeholder (md5(REQUEST_TIME) + two-pass str_replace)
Fixed in 7.9.2 · CVE-2026-116763 · Oct 28, 2026 · Wordfence
medium
Unauthenticated Information Exposure
Fixed in 7.9.1 · CVE-2026-114190 · Oct 23, 2026 · Wordfence
Unauthenticated Stored Cross-Site Scripting
Fixed in 7.9.2 · CVE-2026-113499 · Oct 23, 2026 · Wordfence
Unauthenticated Stored Cross-Site Scripting
Fixed in 7.9.2 · CVE-2026-113500 · Oct 23, 2026 · Wordfence
Missing Authorization
Fixed in 7.9.2 · CVE-2026-113501 · Oct 23, 2026 · Wordfence
medium
Reflected Cross-Site Scripting via ESI 'esi' Parameter
Fixed in 7.9.1 · CVE-2026-76579 · Sep 2, 2026 · Wordfence
high
Unauthenticated Server-Side Request Forgery
Fixed in 7.9.1 · CVE-2026-84761 · Aug 27, 2026 · Wordfence
high
Unauthenticated Stored Cross-Site Scripting via Comment Content
Fixed in 7.9 · CVE-2026-18978 · Aug 27, 2026 · Wordfence
medium
Authenticated (Author+) Stored Cross-Site Scripting via img Tag Attributes
Fixed in 7.8 · CVE-2026-3129 · Aug 27, 2026 · Wordfence
high
Unauthenticated Stored Cross-Site Scripting via QUIC.cloud CCSS/UCSS REST API Endpoints
Fixed in 7.8 · CVE-2026-3375 · May 26, 2026 · Wordfence
medium
Reflected Cross-Site Scripting
Fixed in 7.6 · CVE-2025-12450 · Oct 28, 2025 · Wordfence
medium
Authenticated (Editor+) Server-Side Request Forgery
Fixed in 7.1 · CVE-2025-47437 · May 7, 2025 · Wordfence
medium
Authenticated (Contributor+) Stored Cross-Site Scripting
Fixed in 6.5.3 · CVE-2024-51915 · Dec 20, 2024 · Wordfence
high
Unauthenticated Privilege Escalation
Fixed in 6.5.2 · CVE-2024-50550 · Oct 29, 2024 · Wordfence
medium
Authenticated (Contributor+) Stored Cross-Site Scripting
Fixed in 6.5.1 · CVE-2024-47373 · Sep 30, 2024 · Wordfence
high
Unauthenticated Stored Cross-Site Scripting
Fixed in 6.5.1 · CVE-2024-47374 · Sep 30, 2024 · Wordfence
high
Authenticated (Author+) Path Traversal
Fixed in 6.5.1 · CVE-2024-47637 · Sep 30, 2024 · Wordfence
medium
Authenticated (Administrator+) Stored Cross-Site Scripting
Fixed in 6.5 · CVE-2024-9169 · Sep 24, 2024 · Wordfence
critical
Unauthenticated Sensitive Information Exposure via Log Files
Fixed in 6.5.0.1 · CVE-2024-44000 · Sep 5, 2024 · Wordfence
critical
Unauthenticated Privilege Escalation
Fixed in 6.4 · CVE-2024-28000 · Aug 19, 2024 · Wordfence
medium
Cross-Site Request Forgery to Stored Cross-Site Scripting
Fixed in 6.3 · CVE-2024-3246 · Jul 23, 2024 · Wordfence
high
Unauthenticated Stored Cross-Site Scripting via 'nameservers' and '_msg'
Fixed in 5.7.0.1 · CVE-2023-40000 · Feb 27, 2024 · Wordfence
high
Missing Authorization via update_cdn_status
Fixed in 5.7.0.1 · CVE-2023-45000 · Feb 27, 2024 · Wordfence
medium
Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode
Fixed in 5.7 · CVE-2023-4372 · Oct 23, 2023 · Wordfence
medium
Missing Authorization to Toggle Crawler State
Fixed in 5.3.1 · CVE-2022-46800 · Mar 22, 2023 · Wordfence
medium
Authorization Bypass
Fixed in 4.4.4 · CVE-2021-24964 · Nov 30, 2021 · Wordfence
medium
Reflected Cross-Site Scripting via qc_res
Fixed in 4.4.4 · CVE-2021-24963 · Nov 30, 2021 · Wordfence
Authenticated Stored Cross-Site Scripting (XSS) vulnerability
Fixed in 3.6.1 · Dec 26, 2020 · Patchstack
medium
Authenticated Stored Cross-Site Scripting via IP setting
Fixed in 3.6.1 · CVE-2020-29172 · Dec 26, 2020 · Wordfence

Questions about LiteSpeed Cache’s security

Is LiteSpeed Cache safe to use?

No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep LiteSpeed Cache updated: most attacks target sites that haven’t updated.

Does LiteSpeed Cache have known security vulnerabilities?

None that affect the current version. WPVulnerability’s database lists 30 older issues, fixed in earlier versions, so keep LiteSpeed Cache up to date.

Is LiteSpeed Cache still maintained?

Yes. Its last release was 4 days ago. Its authors resolved 37 of the 76 support threads opened in the last two months.

Is LiteSpeed Cache compatible with the latest WordPress?

Yes. It’s tested up to WordPress 7.1.4, the current version.

Hear about the next one first

Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.

Start free

Vulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.