CVE-2026-113499 LiteSpeed CVE debrief

Who should care

Defenders responsible for WordPress sites using the LiteSpeed Cache plugin should assess exposure and prioritize updating to version 7.9.2 or later. They should also review and restrict HTML rewriting routines to stylesheet content, and monitor for suspicious activity on affected sites. This includes operators, platform administrators, vulnerability management teams, and security teams who need to ensure the security and integrity of their sites.

Why it matters

The LiteSpeed Cache WordPress plugin vulnerability allows unauthenticated users to inject malicious JavaScript code, potentially leading to stored XSS attacks on affected sites.

• Unauthenticated users can inject malicious JavaScript code
• Code execution in the browser of any visitor, including administrators
• Potential for stored XSS attacks on affected sites

Technical summary

The LiteSpeed Cache WordPress plugin before 7.9.2 does not restrict one of its HTML rewriting routines to stylesheet content, allowing unauthenticated users to inject attributes that execute JavaScript in the browser of any visitor. This vulnerability can lead to stored XSS attacks on affected sites. Defenders should prioritize verifying and updating LiteSpeed Cache to version 7.9.2 or later, and monitor for suspicious activity on affected sites. The vulnerability allows unauthenticated users to inject malicious JavaScript code, potentially leading to stored XSS attacks on affected sites.

Defensive priority

Defenders should prioritize verifying and updating LiteSpeed Cache to version 7.9.2 or later, and monitor for suspicious activity on affected sites.

Recommended defensive actions

• Verify and update LiteSpeed Cache to version 7.9.2 or later
• Monitor for suspicious activity on affected sites
• Review and restrict HTML rewriting routines to stylesheet content
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and source item provide details on the vulnerability, but limited information is available on exploitation or affected versions. Defenders should verify and update LiteSpeed Cache to version 7.9.2 or later, and monitor for suspicious activity on affected sites. The vulnerability allows unauthenticated users to inject malicious JavaScript code, potentially leading to stored XSS attacks on affected sites.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.