LiteSpeed Cache <= 7.9 - Unauthenticated Server-Side Request Forgery
Strategic Overview
- Status
- Patched in 7.9.1
- Affected Plugin
- LiteSpeed Cache
- Affected Version
<= 7.9- CVSS
- 7.2High
- Weakness type
- CWE-918 · Server-Side Request Forgery (SSRF)
- CVE
CVE-2026-84761
At a glance
CVE-2026-84761 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in the LiteSpeed Cache WordPress plugin, affecting versions <= 7.9. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 7.9.1; sites on affected versions should update now. Disclosed September 2026, reported by Ayoub Elaich (sicksec).
Vulnerability Overview
The LiteSpeed Cache plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 7.9. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application which can be used to query and modify information from internal services.
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 privileges on the target site, and no interaction from a victim user.
CWE-918: Server-Side Request Forgery (SSRF)
Reaching this weakness in LiteSpeed Cache <= 7.9 takes no account at all. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.
The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For LiteSpeed Cache the fix is 7.9.1: builds <= 7.9 are affected, anything from 7.9.1 onward is not.
Remediation
Update to version 7.9.1, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: LiteSpeed Cache 7.9.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Same weakness class
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-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 - 6.5CVE-2021-24964: LiteSpeed Cache <= 4.4.3 Authorization Bypass
CVE-2021-24964
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C