CVE-2026-109215: litespeedtech LiteSpeed advisory

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

What it is

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.

Description quoted from the CVE record (assigned by Wordfence, published 2026-10-29).

Weakness: CWE-79 Improper Neutralization of Input During Web Page Generation

How it can be exploited

Exploitable over the network with low attack complexity needing low privileges and no user interaction. Impact: confidentiality low, integrity low, availability none. CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: partial.

Public exploit evidence (Exploit Observer)

Exploit Observer found 3 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 6 references on Exploit Observer

Live scores

EPSS: 0.003
low predicted chance of attack
VEDAS: 0.988
strong exploit evidence
On CISA KEV: Not listed
Detection rule: Suricata

Who is affected

Product	Affected	Not affected
litespeedtech LiteSpeed Cache	up to and including 7.9.1	Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.

How to detect it

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-109215 WordPress LiteSpeed Cache - Stored XSS via bbp_reply_content. Add them to your Suricata rule set and reload.

Show the rules

suricata

alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-109215 WordPress LiteSpeed Cache - Stored XSS via bbp_reply_content"; flow:established,to_server; http.method; content:"POST"; http.request_body; content:"bbp_reply_content"; nocase; fast_pattern; pcre:"/bbp_reply_content[^&]*(?:<|%3c)\s*(?:\/?\s*)?(?:img|script|svg|iframe|on[a-z]+\s*(?:=|%3d))/i"; classtype:web-application-attack; reference:cve,CVE-2026-109215; reference:url,https://www.exploit.observer/?keyword=CVE-2026-109215&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=litespeed-cache&match=exact; sid:1105205; rev:1;)

CVE-2026-109215.rules on GitHub

References

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.