Skip to main content
CVE-2024-52724VulnerabilityPublished Updated

CVE-2024-52724: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Dec 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

AI-suggested

Given the absence of an official patch at the time of disclosure, organizations should immediately implement the following mitigations: 1) Employ Web Application Firewalls (WAFs) with rules specifically designed to detect and block SQL injection attempts targeting /q/show.php and similar endpoints. 2) Conduct thorough input validation and sanitization on all user-supplied data, ideally using parameterized queries or prepared statements to prevent injection. 3) Restrict database user privileges to the minimum necessary to limit the impact of potential exploitation. 4) Monitor database logs and web server logs for unusual query patterns or error messages indicative of injection attempts. 5) If possible, isolate the ZZCMS installation in a segmented network zone to reduce lateral movement risk. 6) Stay alert for official patches or updates from ZZCMS maintainers and apply them promptly once available. 7) Consider temporary disabling or restricting access to the vulnerable /q/show.php endpoint if it is not essential to operations. 8) Conduct security assessments and penetration testing focused on injection vulnerabilities to identify and remediate similar issues proactively.

Description

ZZCMS 2023 was discovered to contain a SQL injection vulnerability in /q/show.php.

References

Community reviews

Loading reviews…