Vulnerability record · CVE-2024-44000 · published 20 October 2024
CVE-2024-44000: LiteSpeed Cache WordPress plugin authentication bypass via exposed credentials
Litespeedtech · Litespeed Cache
LiteSpeed Cache versions before 6.5.0.1 contain an insufficiently protected credentials flaw (CWE-522) that allows authentication bypass. The reference describes it as an unauthenticated account takeover vulnerability, so any site running an affected version is exposed to full compromise of user accounts.
Description
Insufficiently Protected Credentials vulnerability in LiteSpeed Technologies LiteSpeed Cache litespeed-cache allows Authentication Bypass.This issue affects LiteSpeed Cache: from n/a through < 6.5.0.1.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Automated analysis
critical priorityCVSS 9.8 with network reachability, no authentication or interaction, and very high EPSS make this an urgent patch-first issue despite no KEV listing.
What it is
LiteSpeed Cache versions before 6.5.0.1 contain an insufficiently protected credentials flaw (CWE-522) that allows authentication bypass. The reference describes it as an unauthenticated account takeover vulnerability, so any site running an affected version is exposed to full compromise of user accounts.
Impact
An unauthenticated attacker can bypass authentication and take over accounts, gaining the privileges of the compromised user, potentially including administrator access to the WordPress site.
Attack surface
Reachable over the network with no authentication and no user interaction required, per the CVSS vector AV:N/AC:L/PR:N/UI:N. The flaw lives in the plugin's handling of credentials, so any site with the affected plugin version is a target.
Exploitation
Not listed in CISA KEV, but EPSS is very high at 0.823 (99.6th percentile), indicating strong likelihood of exploitation activity. The single reference is a Patchstack advisory tagged as an unauthenticated account takeover, which points to active interest even though no public exploit tag is present.
What to do
- Update LiteSpeed Cache to 6.5.0.1 or later immediately.
- If patching is delayed, disable or remove the LiteSpeed Cache plugin until it can be updated.
- Rotate WordPress user passwords and invalidate active sessions after patching, since credentials may already have been exposed.
- Audit administrator accounts and review recent login and user-creation activity for signs of unauthorized access.
- Add virtual patching or WAF rules blocking requests that target the vulnerable credential-handling path if the plugin cannot be updated at once.
Detection
- Review web server and plugin logs for unusual requests to LiteSpeed Cache endpoints, especially from unauthenticated clients.
- Monitor WordPress authentication logs for logins or session creation from unexpected IPs or user agents.
- Check for new or modified administrator accounts and unexpected password reset or role-change events.
- Hunt for outbound connections or file changes consistent with post-exploitation activity on hosts running the affected plugin.
This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.
Affected products
1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
Track CVE-2024-44000 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2024-44000), CISA KEV, FIRST EPSS (scores of 2026-09-24). This page is refreshed as NVD updates the record.