LiteSpeed Cache <= 3.6 - Authenticated Stored Cross-Site Scripting via IP setting
Strategic Overview
- Status
- Patched in 3.6.1
- Affected Plugin
- LiteSpeed Cache
- Affected Version
<= 3.6- CVSS
- 5.5Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2020-29172
At a glance
CVE-2020-29172 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the LiteSpeed Cache WordPress plugin, affecting versions <= 3.6. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). Exploitation requires an authenticated account. The issue is fixed in version 3.6.1; sites on affected versions should update now. Disclosed December 2020, reported by WonTae Jang.
Vulnerability Overview
A cross-site scripting (XSS) vulnerability in the LiteSpeed Cache plugin before 3.6.1 for WordPress can be exploited via the Server IP setting.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in LiteSpeed Cache <= 3.6 takes any authenticated account. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For LiteSpeed Cache the fix is 3.6.1: builds <= 3.6 are affected, anything from 3.6.1 onward is not.
Remediation
Update to version 3.6.1, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to LiteSpeed Cache: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: LiteSpeed Cache 3.6.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
- 7.2CVE-2026-18978: LiteSpeed Cache <= 7.8.1 Stored Cross-Site Scripting
CVE-2026-18978 - 7.2CVE-2026-3375: LiteSpeed Cache <= 7.7 Stored Cross-Site Scripting
CVE-2026-3375 - 7.2CVE-2024-47374: LiteSpeed Cache <= 6.1 Stored Cross-Site Scripting
CVE-2024-47374 - 7.2CVE-2023-40000: LiteSpeed Cache <= 5.7 Stored Cross-Site Scripting
CVE-2023-40000
Other vulnerabilities in LiteSpeed Cache
- 9.8CVE-2024-28000: LiteSpeed Cache <= 6.3.0.1 Privilege Escalation
CVE-2024-28000 - 8.1CVE-2024-50550: LiteSpeed Cache <= 6.5.1 Privilege Escalation
CVE-2024-50550 - 7.5CVE-2024-44000: LiteSpeed Cache <= 6.4.1 Info Exposure
CVE-2024-44000 - 7.2CVE-2026-84761: LiteSpeed Cache <= 7.9 Server-Side Request Forgery
CVE-2026-84761 - 6.5CVE-2021-24964: LiteSpeed Cache <= 4.4.3 Authorization Bypass
CVE-2021-24964 - 6.4CVE-2026-3129: LiteSpeed Cache <= 7.7 Stored Cross-Site Scripting
CVE-2026-3129 - 6.4CVE-2024-51915: LiteSpeed Cache <= 6.5.2 Stored Cross-Site Scripting
CVE-2024-51915 - 6.4CVE-2024-47373: LiteSpeed Cache <= 6.5.0.2 Stored Cross-Site Scripting
CVE-2024-47373
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C