CVE-2024-42599: n/a
Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 1.4% chance of exploitation in 30 days – higher than 72% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 22 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
AI-suggested
To mitigate CVE-2024-42599, organizations should immediately restrict access to the SeaCMS admin interface to trusted users only and enforce strong authentication mechanisms, such as multi-factor authentication (MFA). Conduct a thorough audit of user accounts and remove or disable any unnecessary or inactive accounts. Implement network-level access controls, such as IP whitelisting or VPN requirements, to limit administrative access. Monitor logs for unusual file modification activities or command execution patterns within the CMS environment. Until an official patch is released, consider deploying web application firewalls (WAFs) with custom rules to detect and block attempts to exploit file editing functionalities. Additionally, isolate the CMS server from critical infrastructure to reduce lateral movement risk. Regularly back up CMS data and system configurations to enable recovery in case of compromise. Stay updated with vendor advisories for patch availability and apply updates promptly once released.
Description
SeaCMS 13.0 has a remote code execution vulnerability. The reason for this vulnerability is that although admin_files.php imposes restrictions on edited files, attackers can still bypass these restrictions and write code, allowing authenticated attackers to exploit the vulnerability to execute arbitrary commands and gain system privileges.