Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSubmit crafted comment unauthenticated
-
DeliveryPayload stored via 'comment' parameter
-
ExploitHTML Minify emits into JSON-LD raw-text context
-
ExecutionScript executes in visitor browser
-
ImpactSession hijack or content manipulation
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires two specific conditions stated in the description: the LiteSpeed Cache HTML Minify option (O_OPTM_HTML_MIN) must be enabled, AND a companion plugin must render the stored comment content into a raw-text context such as a JSON-LD script block on the same page. Without both, the injected payload is not placed into an executable context. The injection point is the 'comment' parameter and does not require authentication (PR:N), but these non-default configuration requirements - plus dependence on a secondary plugin's output behavior - are the primary factors limiting real-world exploitability and underpin the AC:H rating. Affected: all LiteSpeed Cache versions up to and including 7.9.1. |
| Impact | This is a moderate-severity Stored XSS (CVSS 5.4) that is realistically lower-priority than the CVSS score alone might suggest, because exploitation is heavily conditional. The CVSS vector (AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N) shows a network, unauthenticated vector but explicitly flags high attack complexity (AC:H) and a scope change (S:C) reflecting script execution in a victim's browser rather than on the server. The AC:H is corroborated by the description: the flaw is only reachable when the HTML Minify option (O_OPTM_HTML_MIN) is enabled AND a companion plugin renders stored comment content into a raw-text context such as a JSON-LD script block on the same page. No EPSS score is provided in the input, there is no CISA KEV listing, and no confirmed public exploit code is present - the references are the Wordfence advisory, plugin source lines, and the fix changeset, not a working PoC. The vuln.today decision label is 'this_month', consistent with a real but non-emergency issue. Net assessment: a genuine unauthenticated stored-XSS requiring a specific, non-default configuration plus a secondary plugin - prioritize patching on a normal cycle rather than as an emergency, with urgency raised for sites known to run HTML Minify alongside a JSON-LD/structured-data plugin. |
| Exploit ScenarioDerived | An unauthenticated attacker submits a comment containing a crafted script payload to a WordPress site running LiteSpeed Cache with HTML Minify enabled. If a companion plugin writes that stored comment text into a raw-text context such as a JSON-LD script block on a cached page, the injected script executes in the browser of any visitor who loads that page, enabling session theft or actions in the victim's context. No public exploit code is identified in the provided data; exploitation also depends on the specific HTML Minify plus companion-plugin combination, consistent with the AC:H rating. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 29, 2026
Stored cross-site scripting in the LiteSpeed Cache plugin for WordPress (all versions up to and including 7.9.1) lets an unauthenticated attacker submit a crafted 'comment' value that the plugin's HTML Minify routine fails to sanitize or escape, so the payload is preserved in cached output rather than neutralized. The script executes only when two non-default conditions coincide: the HTML Minify option (O_OPTM_HTML_MIN) is enabled, and a companion plugin renders the stored comment into a raw-text context such as a JSON-LD script block on the same page. Rated CVSS 5.4 with AC:H reflecting that dependency chain; there is no CISA KEV listing and no public exploit identified at time of analysis, so this is a moderate-priority, configuration-dependent issue rather than an actively exploited one.
RemediationAI
A fix has landed upstream in the LiteSpeed Cache repository - see the WordPress.org changeset at https://plugins.trac.wordpress.org/changeset?reponame=&old=3757253%40litespeed-cache&new=3757253%40litespeed-cache - so an upstream fix is available (changeset); a released patched version number is not independently confirmed from the supplied data, so verify the current plugin version and changelog before upgrading. Until a patched build is verified, the actionable mitigation follows directly from the exploitation preconditions: disable the HTML Minify option (O_OPTM_HTML_MIN) in the LiteSpeed Cache settings, which removes the code path that preserves the unsanitized comment markup; the trade-off is the loss of HTML minification and its page-size/performance benefit. Where minification must stay on, identify and remove or reconfigure the companion plugin that emits stored comment content into raw-text contexts such as JSON-LD script blocks, since without that rendering the injected value never reaches an executable context. Both measures are degradations of site functionality rather than complete fixes, and the vendor's patched release remains the definitive remedy.
Affected VersionsENISA
Affected Packages
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 flaw is CWE-79 (Improper Neutralization of Input During Web Page Generation) in LiteSpeed Cache's HTML minification pipeline. The referenced source in tags/7.9.1 shows the minifier logic in lib/html-min.cls.php (around lines 103, 173 and 205) invoked from src/optimize.cls.php (line 525) and src/optimizer.cls.php (line 57); the minifier rewrites and re-emits page markup, and the 'comment' parameter can survive that rewriting without adequate input sanitization or output escaping. Because the vulnerable component is not the only party involved, the CVSS vector carries S:C (scope changed) with C:L/I:L/A:N - the injected markup can affect a context belonging to another component on the page. The executable context is only reached when a separate companion plugin writes the stored comment content into a raw-text region such as a JSON-LD script block; a benign HTML context would not yield the same execution path. Trigger specifics beyond that configuration dependency are not described in the available sources, and the AC:H metric reflects the requirement that both the minify option and the companion plugin's raw-text rendering be present on the same page.
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
AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
Unauthenticated comment injection gives PR:N; the required HTML Minify setting plus companion-plugin raw-text rendering justify AC:H; browser execution yields S:C with C:L/I:L and no availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The LiteSpeed Cache plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 7.9.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This vulnerability is only exploitable when the HTML Minify option (O_OPTM_HTML_MIN) is enabled and a companion plugin renders stored comment content into a raw-text context such as a JSON-LD script block on the same page.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Litespeed Cache
View allAuthentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
Privilege escalation in LiteSpeed Cache plugin for WordPress (versions up to and including 6.3.0.1) allows unauthenticat
Stored cross-site scripting in LiteSpeed Cache for WordPress (versions up to and including 5.7) allows remote unauthenti
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in LiteSpeed Technolo
Relative Path Traversal vulnerability in LiteSpeed Technologies LiteSpeed Cache litespeed-cache allows Path Traversal.4.
Incorrect Privilege Assignment vulnerability in LiteSpeed Technologies LiteSpeed Cache litespeed-cache allows Privilege
Missing Authorization vulnerability in LiteSpeed Technologies LiteSpeed Cache.7. Rated high severity (CVSS 8.2), this vu
Stored XSS in the LiteSpeed Cache WordPress plugin (all versions through 7.8.1) allows unauthenticated attackers to perm
Unauthenticated SSRF in the LiteSpeed Cache WordPress plugin (versions ≤ 7.9) allows any remote attacker without credent
The LiteSpeed Cache plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'esi' shortcode in version
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in LiteSpeed Technolo
Stored cross-site scripting in the LiteSpeed Cache plugin for WordPress (all versions up to and including 7.9.1) lets au
EUVD-2026-112690
GHSA-wgrw-7pq3-7r4q
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB