CVE-2026-18978

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

Published Aug 28, 2026 CVSS 3.1 · 7.2 High EPSS < 1% KEV · Not listed
Description
The LiteSpeed Cache plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content in all versions up to, and including, 7.8.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. A comment payload crafted exclusively from decimal numeric character references (e.g. &#34;, &#60;, &#62;) placed inside an allowed element such as &lt;code&gt; bypasses WordPress's wp_kses sanitization, as kses does not treat a data-settings="..." substring within text content as an HTML attribute, allowing the malicious payload to reach the vulnerable function. For this to be exploitable, the site must allow users with previously approved comments to write new comments, and the require_name_email setting must be disabled.

Analysis

AI-generated

Technical impact

The LiteSpeed Cache WordPress plugin contains a stored cross‑site scripting flaw that allows attackers to inject scripts through comment content. The vulnerability is caused by insufficient input sanitization and output escaping, allowing an attacker to embed a payload consisting only of decimal numeric character references inside a permitted element such as &lt;code&gt;. When a comment containing such a payload is saved, the script is stored and subsequently rendered on pages that display the comment, leading to arbitrary script execution in the browsers of users who view that content.

Affected Systems

All versions of the LiteSpeed Cache plugin up to and including 7.8.1 are affected. The issue was discovered in the plugin coded by litespeedtech and affects WordPress sites that use this plugin for caching and comment handling.

Risk and Exploitability

The flaw carries a CVSS score of 7.2, indicating a high severity impact. No EPSS score is publicly available and the vulnerability is not included in CISA’s KEV catalog. Exploitation requires that the WordPress site allows users with previously approved comments to write new comments and that the require_name_email setting is disabled. Attackers can deliver the payload via the comment form; the stored XSS then executes when any visitor loads an affected page, potentially allowing credential theft, defacement, or other malicious actions. Given the lack of a known public exploit but high CVSS, the risk remains high if the conditions are met.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade LiteSpeed Cache to the latest release, which removes the stored‑XSS vulnerability
  • If an immediate upgrade is not possible, disable new comment posting or restrict comment submissions to administrators only to prevent injection of malicious payloads
  • Ensure the require_name_email configuration is enabled, or otherwise enforce an additional verification step before comment content is stored

Generated by OpenCVE AI on August 28, 2026 at 14:43 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Litespeedtech
Litespeedtech litespeed Cache
Wordpress
Wordpress wordpress
Vendors & Products Litespeedtech
Litespeedtech litespeed Cache
Wordpress
Wordpress wordpress
Type Values Removed Values Added
Description The LiteSpeed Cache plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content in all versions up to, and including, 7.8.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. A comment payload crafted exclusively from decimal numeric character references (e.g. &#34;, &#60;, &#62;) placed inside an allowed element such as &lt;code&gt; bypasses WordPress's wp_kses sanitization, as kses does not treat a data-settings="..." substring within text content as an HTML attribute, allowing the malicious payload to reach the vulnerable function. For this to be exploitable, the site must allow users with previously approved comments to write new comments, and the require_name_email setting must be disabled.
Title LiteSpeed Cache <= 7.8.1 - Unauthenticated Stored Cross-Site Scripting via Comment Content
Weaknesses CWE-79
References
Metrics cvssV3_1

{'score': 7.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N'}

Weaknesses
  • CWE-79

    Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Sources

Status
PUBLISHED
Assigner
Wordfence
Published
Updated
Aug 28, 2026, 3:56 PM
Reserved
Aug 5, 2026, 4:34 PM
Status
Deferred
Published
Aug 28, 2026, 5:16 AM
Modified
Aug 28, 2026, 8:17 PM