Skip to main content
VulnerabilityPublished

CVE-2026-113500: LiteSpeed Cache (WordPress plugin) · Cross-site Scripting

Affects LiteSpeed Cache (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 7.9.2 soon.

Data as of 29 Oct 2026, 19:15 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.17.5
EPSS
0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 7.9.2
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade LiteSpeed Cache (WordPress plugin) to 7.9.2.

Affected software

ProductAffectedFixed in
LiteSpeed CacheAffected
  • <7.9.2
Fixed in
  • 7.9.2

AI-suggested

A fix is available in LiteSpeed Cache version 7.9.2. Users should upgrade to version 7.9.2 or later to remediate this vulnerability. Until then, disabling the HTML optimization feature that triggers this issue may reduce risk. Patch status is confirmed by the versioning information indicating the vulnerability affects versions before 7.9.2.

Description

The LiteSpeed Cache WordPress plugin before 7.9.2 does not limit one of its HTML optimization routines to stylesheet content, so it can delete the markup that closes an attribute in the rendered page, and combined with unescaped comment author output this allows unauthenticated users whose comments are published to inject event-handler attributes that run JavaScript in the browser of any visitor, including a logged-in administrator, viewing front-end pages while the optimization is enabled.

References

Community reviews

Loading reviews…