Skip to main content
CVE-2024-44817VulnerabilityPublished

CVE-2024-44817: ZZCMS · n/a

Affects ZZCMSSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Sep 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-25.

What to do

Affected software

ProductAffectedFixed in
GitHubgkdgkd123/ZZCMSpkg:github/gkdgkd123/ZZCMSOther threatsAffected
  • <=2023
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until an official patch for CVE-2024-44817 is released, organizations should implement multiple layers of defense. First, apply strict input validation and sanitization on all user-supplied parameters, especially the 'id' parameter in adv2.php, to block malicious SQL payloads. Employ parameterized queries or prepared statements in the application code to prevent SQL Injection. Deploy a Web Application Firewall (WAF) configured to detect and block SQL Injection attempts targeting ZZCMS components. Conduct thorough code reviews and security testing focusing on database interactions. Restrict database user permissions to the minimum necessary to limit the impact of potential exploitation. Monitor database logs and web server logs for unusual query patterns or error messages indicative of injection attempts. Additionally, isolate the CMS environment from critical internal networks to reduce lateral movement risk. Prepare an incident response plan specific to SQL Injection attacks and keep abreast of vendor updates for timely patch application.

Description

SQL Injection vulnerability in ZZCMS v.2023 and before allows a remote attacker to obtain sensitive information via the id parameter in the adv2.php component.

References

Community reviews

Loading reviews…