Skip to content
major vulnerability· requires attention

High-severity (CVSS 9.8) unauthenticated privilege escalation in a widely deployed WordPress caching plugin that can lead to site takeover; broad web impact and public exploit info.

Web

CVE-2024-28000

9.8
Critical
EPSS 68%Patch availableSep 1, 2026

Unauthenticated privilege escalation in LiteSpeed Cache WordPress plugin (<=6.3.0.1).

common questions

Is CVE-2024-28000 being exploited?

Not confirmed. CVE-2024-28000 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 68% probability of exploitation in the next 30 days.

How severe is CVE-2024-28000?

CVE-2024-28000 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2024-28000?

Yes. A fix has been recorded for CVE-2024-28000. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2024-28000 affect?

CVE-2024-28000 affects LiteSpeed Cache plugin (<= 6.3.0.1), WordPress sites using LiteSpeed Cache. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2024-28000?

Update LiteSpeed Cache to fixed version (>6.3.0.1) or disable plugin until patched.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
LiteSpeed Cache plugin (<= 6.3.0.1)WordPress sites using LiteSpeed Cache
impact

Unauthenticated attacker can escalate to admin on affected WordPress sites, enabling site takeover, remote code execution, defacement, or data theft.

action required

Immediate action required

affected versions
LiteSpeed Technologies LiteSpeed Cache
  • affected<= 6.3.0.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free