CVE-2026-109215: LiteSpeed Cache (WordPress plugin) · Cross-site Scripting
Affects LiteSpeed Cache (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 6.4 Medium.
Data as of 29 Oct 2026, 19:15 UTC
Thin evidence
One scorer or none| CNA (Wordfence) | CVSS 3.1 | 6.4 |
|---|
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| litespeedtechLiteSpeed Cache | Affected
| Fixed in– |
AI-suggested
Users should consider disabling the Viewport Images (VPI) feature or avoid configuring VPI filenames that can be referenced by user-generated content until a fix is available. Restricting subscriber-level users from posting raw img tags in bbPress topics may also reduce risk. Monitor vendor advisories for updates and apply patches once released.
Description
The LiteSpeed Cache plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'bbp_reply_content' parameter in all versions up to, and including, 7.9.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires that an administrator has enabled Viewport Images (VPI) and configured a VPI filename that matches an image the attacker can embed in user-generated content — such as a bbPress topic where Subscriber-level Participants are permitted to post replies containing raw img tags.
References
- wordfence.com/threat-intel/vulnerabilities/id/8bf9b130-bb1e-43fc-b5c9-337646b8976e?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/litespeed-cache/tags/7.9.1/src/media.cls.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/litespeed-cache/tags/7.9.1/src/media.cls.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/litespeed-cache/tags/7.9.1/src/utility.cls.php (opens in a new tab)
- github.com/litespeedtech/lscache_wp/commit/0fc5f9ad69a138b8ee1fe2d07a5e9ac2574e1eb0 (opens in a new tab)
- plugins.trac.wordpress.org/browser/litespeed-cache/tags/7.9.2/src/media.cls.php (opens in a new tab)