CVE-2024-24621

CVE-2024-24621 is a critical-severity vulnerability in Softaculous Webuzo with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-697.

Key facts

Description

Softaculous Webuzo contains an authentication bypass vulnerability through the password reset functionality. Remote, anonymous attackers can exploit this vulnerability to gain full server access as the root user.

Frequently asked questions

What is CVE-2024-24621?
Softaculous Webuzo contains an authentication bypass vulnerability through the password reset functionality. Remote, anonymous attackers can exploit this vulnerability to gain full server access as the root user.
How severe is CVE-2024-24621?
CVE-2024-24621 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2024-24621 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (63rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-24621?
CVE-2024-24621 affects Softaculous Webuzo. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2024-24621?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2024-24621 have an EU (EUVD) identifier?
Yes. CVE-2024-24621 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-22022.
When was CVE-2024-24621 published?
CVE-2024-24621 was published on 2024-07-25 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Softaculous Webuzo

All CVEs affecting Softaculous Webuzo →

Other CWE-697 vulnerabilities

Browse all CWE-697 vulnerabilities →