Skip to main content
VulnerabilityPublished Updated

CVE-2024-46640: SeaCMS · Code Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 62% 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 20 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

AI-suggested

  1. Immediate mitigation involves restricting access to the SeaCMS management interfaces and MySQL slow query logging features to trusted IP addresses only.
  2. Disable MySQL slow query logging temporarily if feasible, to prevent exploitation via this vector.
  3. Monitor slow query logs and web server logs for unusual or suspicious entries indicative of injection attempts.
  4. 5. Implement Web Application Firewall (WAF) rules to detect and block payloads targeting the sql.class.chp file or suspicious MySQL slow query injection patterns. 6. Conduct thorough security audits and code reviews of the affected components to identify and remediate similar logic flaws. 7. Employ network segmentation to limit the impact of a potential compromise. 8. Prepare incident response plans specifically for RCE scenarios involving SeaCMS. 9. Educate administrators about the risk and signs of exploitation to enable rapid detection and response. These steps go beyond generic advice by focusing on the unique exploitation vector via MySQL slow query logging and the specific vulnerable component.

Description

SeaCMS 13.2 has a remote code execution vulnerability located in the file sql.class.chp. Although the system has a check function, the check function is not executed during execution, allowing remote code execution by writing to the file through the MySQL slow query method.

References

Community reviews

Loading reviews…