Skip to main content
VulnerabilityPublished

CVE-2024-44921: SeaCMS · SQL Injection

Affects SeaCMSSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 50% 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 3 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubnn0nkey/SeaCMSpkg:github/nn0nkey/SeaCMSOther threatsAffected
  • =12.9
Fixed in–

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

AI-suggested

Since no official patches are currently available, organizations should immediately implement the following mitigations: 1) Apply strict input validation and sanitization on the 'id' parameter to block malicious SQL payloads. 2) Deploy and configure a Web Application Firewall (WAF) with rules targeting SQL injection patterns, especially on the vulnerable endpoint. 3) Restrict access to the /dmplayer/dmku/index.php?ac=del endpoint using IP whitelisting or authentication mechanisms where feasible. 4) Monitor web server and database logs for suspicious activities indicative of SQL injection attempts. 5) Conduct a thorough security audit of SeaCMS installations and consider temporary disabling or isolating vulnerable modules until patches are released. 6) Stay updated with SeaCMS vendor announcements for official patches or security advisories. 7) Educate development and operations teams on secure coding practices to prevent similar vulnerabilities in the future.

Description

SeaCMS v12.9 was discovered to contain a SQL injection vulnerability via the id parameter at /dmplayer/dmku/index.php?ac=del.

References

Community reviews

Loading reviews…