Skip to main content

LiteSpeed Cache CVE-2026-114190

| EUVDEUVD-2026-109251 MEDIUM
Insertion of Sensitive Information Into Sent Data (CWE-201)
2026-10-24 Patchstack GHSA-hcp4-xh6h-xqrq
5.9
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify site running vulnerable LiteSpeed Cache
  2. Exploit
    Craft request meeting complex trigger condition
  3. Execution
    Induce plugin to embed sensitive data in response
  4. Impact
    Extract disclosed sensitive information

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Outbound data filtering
Exploitation Conditions

The available sources (CWE-201, 'Retrieve Embedded Sensitive Data') establish that the plugin inserts sensitive information into data it sends, but the exact feature, endpoint, request, or configuration that triggers the disclosure is not described in the available sources. The CVSS metrics indicate no authentication (PR:N) and no user interaction (UI:N) are required, so the limiting factor is the high attack complexity (AC:H): exploitation depends on a non-trivial condition that is not spelled out in the evidence, rather than being a simple default-configuration read. Exploitation is confined to sites running LiteSpeed Cache versions from an unspecified start through 7.9.

Impact

This is a moderate-severity information-disclosure flaw (CVSS 5.9) in the LiteSpeed Cache WordPress plugin, reported by Patchstack. The CVSS vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N indicates a network-reachable, unauthenticated issue with high confidentiality impact but no integrity or availability impact - and critically AC:H (high attack complexity), which materially dampens real-world exploitability. The signals are largely consistent and point to a bounded risk: there is no CISA KEV listing and no EPSS score was supplied, so there is no evidence of active or probable mass exploitation. The only reference is a Patchstack advisory entry, which is a vulnerability catalog record, not verified working exploit code. The vuln.today decision label is 'this_month', signaling routine prioritization rather than emergency action. Net assessment: despite the unauthenticated network vector, the combination of high attack complexity, confidentiality-only impact, no KEV, and no public exploit makes this a patch-in-normal-cycle item rather than a drop-everything emergency - the main counterweight is the plugin's very large install base, which raises aggregate exposure. Note that the description does not explain how the sensitive data is exposed, so the precise trigger cannot be confirmed from the available sources.

Exploit ScenarioDerived

A remote, unauthenticated attacker interacts with a site running a vulnerable LiteSpeed Cache version (through 7.9) and, under the specific non-trivial conditions implied by the high attack complexity, is able to retrieve embedded sensitive data that the plugin inserts into data it sends (CWE-201). No public exploit code has been identified, and the exact request or mechanism needed to trigger the disclosure is not described in the available sources. Because no authentication or user interaction is required (PR:N/UI:N), a successful technique would be reusable across exposed sites.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 24, 2026

LiteSpeed Cache, the WordPress caching plugin maintained by Hai Zheng, inserts sensitive information into the data it sends back to clients, exposing content that should not be readable by outside parties in releases through 7.9. The CVSS 5.9 score pairs high confidentiality impact with high attack complexity, so while the flaw can be reached unauthenticated over the network with no user interaction, exploitation depends on a specific condition the public sources do not describe. No public exploit was identified at time of analysis, and the single Patchstack reference does not list a fixed version, so any site currently running LiteSpeed Cache 7.9 or earlier remains in scope.

RemediationAI

The available data does not list a fixed version or a vendor-supplied workaround for this disclosure, so administrators should verify the current release status directly with the vendor and consult the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/litespeed-cache/vulnerability/wordpress-litespeed-cache-plugin-7-9-sensitive-data-exposure-vulnerability?_s_id=cve before relying on an upgrade as the complete fix. Because the sources do not identify which feature, endpoint, or configuration emits the sensitive data, there is no specific setting that can be selectively disabled to close the exposure; the only concrete compensating action supported by the evidence is to deactivate the LiteSpeed Cache plugin on affected installations until a patched release is confirmed, with the clear trade-off that deactivation removes page caching and the associated performance gains and may expose the origin server to higher load. Any such change should be validated in staging first, and given the this-month priority assigned to this CVE, remediation should be scheduled into the current monthly maintenance cycle rather than treated as an immediate emergency.

Affected VersionsENISA

LiteSpeed Cache 0 ≤7.9

Affected Packages

euvd litespeed_cache no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The issue is an instance of CWE-201 (Insertion of Sensitive Information Into Sent Data) in a WordPress plugin, meaning the plugin constructs outbound responses that include data it should have withheld rather than an injection or memory-safety defect. The CPE string cpe:2.3:a:hai_zheng_/_lite_speed_cache:litespeed_cache:*:*:*:*:*:*:*:* identifies the affected package as the LiteSpeed Cache plugin itself (the vendor field is encoded as Hai Zheng / Lite Speed Cache), with a wildcard version, so the CPE alone does not pin a lower bound; the description states the range runs from n/a through 7.9. The vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N shows the disclosure is reachable over the network without credentials and without user interaction, and that impact is confined to confidentiality with no integrity or availability effect. The high attack complexity metric is the limiting factor, but the exact feature, endpoint, request shape, or configuration that causes the over-disclosure is not described in the available sources, so the trigger cannot be reconstructed from the evidence provided and should not be assumed to be a simple default-configuration read.

Know when Litespeed Cache gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 5.9 MEDIUM
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 5.9 MEDIUM

Network-reachable and unauthenticated (AV:N/PR:N/UI:N); AC:H because the trigger is an undescribed non-trivial condition; confidentiality-only disclosure, so C:H and I:N/A:N.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

DescriptionCVE.org

Insertion of Sensitive Information Into Sent Data vulnerability in Hai Zheng / Lite Speed Cache LiteSpeed Cache litespeed-cache allows Retrieve Embedded Sensitive Data.This issue affects LiteSpeed Cache: from n/a through 7.9.

Threat Intelligence Overview

EPSS Score
0.3%
Top 75% exploitable
Prevalence
High
LiteSpeed Cache is one of the most-installed WordPress plugins, millions of active sites
Social Media
1
Sightings
Data Quality
7 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
High
Technical Impact
Partial

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +30
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2024-44000 CRITICAL POC
9.8 Oct 20

Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote

CVE-2024-28000 CRITICAL POC
9.8 Aug 21

Privilege escalation in LiteSpeed Cache plugin for WordPress (versions up to and including 6.3.0.1) allows unauthenticat

CVE-2023-40000 HIGH POC
8.3 Apr 16

Stored cross-site scripting in LiteSpeed Cache for WordPress (versions up to and including 5.7) allows remote unauthenti

CVE-2024-47374 HIGH POC
7.1 Oct 05

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in LiteSpeed Technolo

CVE-2024-47637 HIGH
8.8 Oct 16

Relative Path Traversal vulnerability in LiteSpeed Technologies LiteSpeed Cache litespeed-cache allows Path Traversal.4.

CVE-2024-50550 HIGH
8.1 Oct 29

Incorrect Privilege Assignment vulnerability in LiteSpeed Technologies LiteSpeed Cache litespeed-cache allows Privilege

CVE-2023-45000 HIGH
8.2 Apr 16

Missing Authorization vulnerability in LiteSpeed Technologies LiteSpeed Cache.7. Rated high severity (CVSS 8.2), this vu

CVE-2026-18978 HIGH
7.2 Aug 28

Stored XSS in the LiteSpeed Cache WordPress plugin (all versions through 7.8.1) allows unauthenticated attackers to perm

CVE-2026-84761 HIGH
7.2 Sep 03

Unauthenticated SSRF in the LiteSpeed Cache WordPress plugin (versions ≤ 7.9) allows any remote attacker without credent

CVE-2023-4372 MEDIUM
6.4 Jan 11

The LiteSpeed Cache plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'esi' shortcode in version

CVE-2024-47373 MEDIUM
6.5 Oct 05

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in LiteSpeed Technolo

CVE-2026-3129 MEDIUM
6.4 Aug 28

Stored Cross-Site Scripting in LiteSpeed Cache for WordPress (all versions through 7.7) allows authenticated attackers h

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy