Skip to main content
VulnerabilityPublished Updated

CVE-2024-39027: CMS · SQL Injection

Affects CMSSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% 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:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Jul 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
GitHubseacms-net/CMSpkg:github/seacms-net/CMSOther 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

  1. Immediate mitigation involves restricting access to the vulnerable endpoint (/js/player/dmplayer/dmku/index.php?ac=edit) via web application firewalls (WAFs) or network-level controls to block suspicious requests containing SQL injection patterns targeting the 'cid' parameter.
  2. Implement input validation and parameterized queries in the application code to sanitize and properly handle user-supplied input, eliminating injection vectors.
  3. Monitor web server and database logs for unusual query patterns or access attempts to the vulnerable URL to detect potential exploitation attempts.
  4. If possible, isolate the SeaCMS instance in a segmented network zone to limit exposure.
  5. Stay alert for official patches or security advisories from SeaCMS developers and apply updates promptly once available.
  6. Conduct a thorough security audit of the CMS and underlying infrastructure to identify and remediate any other potential vulnerabilities.
  7. Educate developers and administrators on secure coding practices to prevent similar injection flaws in the future.

Description

SeaCMS v12.9 has an unauthorized SQL injection vulnerability. The vulnerability is caused by the SQL injection through the cid parameter at /js/player/dmplayer/dmku/index.php?ac=edit, which can cause sensitive database information to be leaked.

References

Community reviews

Loading reviews…