CVE-2024-41444: CMS · SeaCMS v12.9 has a SQL injection
Affects CMSSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 42% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 26 Aug 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
GitHubseacms-net/CMSpkg:github/seacms-net/CMSOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Monitor SeaCMS vendor communications closely and apply official patches or updates addressing CVE-2024-41444 immediately upon release.
- Until patches are available, implement a Web Application Firewall (WAF) with robust SQL injection detection and prevention rules tailored to block malicious payloads targeting the 'key' parameter.
- Conduct thorough input validation and sanitization on all user-supplied data, especially parameters used in SQL queries, employing parameterized queries or prepared statements where possible.
- Restrict database user permissions to the minimum necessary to limit the impact of potential SQL injection exploitation.
- Perform regular security assessments and penetration testing focused on injection flaws to identify and remediate similar vulnerabilities.
- Monitor logs for unusual database query patterns or errors indicative of attempted SQL injection attacks.
- Educate development teams on secure coding practices to prevent injection vulnerabilities in future releases.
- Consider isolating SeaCMS instances behind reverse proxies or VPNs if public exposure is not required, reducing attack surface.
Description
SeaCMS v12.9 has a SQL injection vulnerability in the key parameter of /js/player/dmplayer/dmku/index.php?ac=so.