CVE-2024-39154: cms2 · Cross-Site Request Forgery (CSRF)
Affects cms2Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 27 Jun 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 |
|---|---|---|
GitHubthirtypenny77/cms2pkg:github/thirtypenny77/cms2Other 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
To mitigate CVE-2024-39154, organizations should implement several targeted measures beyond generic CSRF protections. First, apply strict anti-CSRF tokens on all state-changing administrative endpoints, ensuring that each request includes a unique, unpredictable token validated server-side. Restrict access to the admin panel by IP whitelisting or VPN-only access to reduce exposure. Enforce multi-factor authentication (MFA) for all administrator accounts to reduce the risk of session hijacking. Educate administrators about phishing and social engineering risks to minimize user interaction exploitation. Regularly audit logs for unusual deletion requests or activity patterns. Finally, monitor vendor announcements for patches or updates and apply them promptly once released. Consider isolating or segmenting the CMS environment to limit lateral movement if compromise occurs.
Description
idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component /admin/keyWord_deal.php?mudi=del&dataType=word&dataTypeCN.