How severe is CVE-2024-44000?

CVE-2024-44000 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2024-44000?

Affected package information for CVE-2024-44000 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2024-44000?

No fixed version has been published for CVE-2024-44000 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2024-44000 actively exploited in the wild?

Yes. There are 9 known exploit references for CVE-2024-44000, including 1 documented proof-of-concept exploit on Exploit-DB and 5 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2024-44000?

CVE-2024-44000 has an EPSS (Exploit Prediction Scoring System) score of 92.8%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2024-44000?

CVE-2024-44000 is classified as CWE-522 (CWE-522). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2024-44000?

CVE-2024-44000 affects litespeedtech litespeed cache. Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2024-44000?

A Nuclei detection template exists for CVE-2024-44000, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2024-44000 published, and has it been updated?

CVE-2024-44000 was published on October 20, 2024 and was last updated on April 23, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2024-44000

CRITICAL

Insufficiently Protected Credentials vulnerability in LiteSpeed Technologies LiteSpeed Cache litespeed-cache allows Authentication Bypass.This issue affects LiteSpeed Cache: from n/a…

Published

Oct 20, 2024

Updated

Apr 23, 2026

Affected

0 pkgs

Patched

None yet

Exploits

9 known

EPSS Exploitation Probability

via FIRST.org ↗

92.8%probability of exploitation in next 30 days

Very High Risk100th percentile+0.46%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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.

Affected Products

1 product · 1 configurations

Application

litespeed cachelitespeedtech

< 6.5.0.1

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-52099webappsphp

Litespeed Cache 6.5.0.1 - Authentication Bypass

by Caner Tercan · Mar 28, 2025

Exploit-DB Source

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2024-44000 in your stack?

O3 detects CVE-2024-44000 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works