Skip to content
Fencer Intel
critical 9.8

CVE-2024-28000 in the critical feed json

WordPress LiteSpeed Cache plugin <= 6.3.0.1 - Unauthenticated Privilege Escalation vulnerability

published 2y ago modified 4mo ago also EUVD-2024-25174

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
68.3%
EPSS 68.3% chance of exploitation in 30 days, percentile 99.3%
public exploits
1
Exploit-DB

Summary

Incorrect Privilege Assignment vulnerability in LiteSpeed Technologies LiteSpeed Cache litespeed-cache.This issue affects LiteSpeed Cache: from n/a through <= 6.3.0.1.

Patch / fix

  • LiteSpeed Technologies LiteSpeed Cache 6.4

Is CVE-2024-28000 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. Published
  2. First public exploit (EDB-52328)

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
total
Assessed
2y ago

Exploit prediction

68.27% chance of exploitation in the next 30 days, higher than 99.3% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • EDB-52328 Litespeed Cache WordPress Plugin 6.3.0.1 - Privilege Escalation webapps, 2025-06-15

CVSS scores

assigned by version score vector
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • LiteSpeed Technologies LiteSpeed Cache
  • litespeedtech litespeed_cache

Classification

Weakness
  • CWE-266 Incorrect Privilege Assignment
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.