CVE-2024-39158: 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, 13:47 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-39158, organizations should implement multiple layers of defense: 1) Apply any available patches or updates from the idccms vendor as soon as they are released. 2) If patches are not yet available, implement web application firewall (WAF) rules to detect and block suspicious CSRF attempts targeting /admin/userSys_deal.php. 3) Enforce strict CSRF protections by ensuring all state-changing requests require a unique, unpredictable CSRF token validated on the server side. 4) Restrict administrative interface access to trusted IP addresses or VPN-only access to reduce exposure. 5) Validate HTTP Referer headers on sensitive endpoints to confirm requests originate from legitimate sources. 6) Educate administrators to avoid clicking on untrusted links or visiting suspicious websites while logged into the CMS. 7) Monitor logs for unusual administrative activity that could indicate exploitation attempts. 8) Consider implementing multi-factor authentication (MFA) for administrative accounts to reduce risk from compromised credentials. These targeted measures go beyond generic advice by focusing on the specific vulnerable endpoint and attack vector.
Description
idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component /admin/userSys_deal.php?mudi=infoSet.