Skip to main content
CVE-2024-29275VulnerabilityPublished Updated

CVE-2024-29275: CMS · n/a

Affects CMSSource 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
4.9% chance of exploitation in 30 days – higher than 92% 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 22 Mar 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

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 should include restricting access to the vulnerable 'id' parameter by implementing web application firewalls (WAFs) with SQL injection detection and blocking rules tailored for SeaCMS. 2. Employ input validation and parameterized queries or prepared statements in the application code to prevent injection attacks. 3. Monitor web server and database logs for suspicious activities targeting the 'id' parameter or unusual SQL query patterns. 4. Isolate the SeaCMS environment from critical internal networks to limit lateral movement in case of compromise. 5. Regularly back up databases and application data to enable recovery in the event of data loss or corruption. 6. Engage with SeaCMS developers or community to obtain or request official patches or updates addressing this vulnerability. 7. Conduct penetration testing and vulnerability scanning focused on SQL injection vectors to identify and remediate similar issues. 8. Educate development and security teams about secure coding practices to prevent future injection flaws.

Description

SQL injection vulnerability in SeaCMS version 12.9, allows remote unauthenticated attackers to execute arbitrary code and obtain sensitive information via the id parameter in class.php.

References

Community reviews

Loading reviews…