CVE-2024-40034: cms · Cross-Site Request Forgery (CSRF)
Affects cmsSource 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 21% 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 9 Jul 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 |
|---|---|---|
GitHubpangchunyuhack/cmspkg:github/pangchunyuhack/cmsOther 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-40034 effectively, organizations should implement the following specific measures: 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 requests targeting /admin/userLevel_deal.php with the mudi=del parameter, especially those lacking valid CSRF tokens or originating from untrusted sources. 3) Enforce strict CSRF protections by validating anti-CSRF tokens on all state-changing requests in the admin interface. 4) Restrict administrative access to trusted IP ranges or VPNs to reduce exposure. 5) Educate administrators about the risks of clicking on untrusted links and encourage the use of multi-factor authentication to reduce the impact of compromised sessions. 6) Monitor logs for unusual activity related to user level modifications and investigate anomalies promptly. 7) Consider implementing Content Security Policy (CSP) headers to mitigate the risk of malicious script execution that could facilitate CSRF attacks. These targeted actions go beyond generic advice and focus on immediate risk reduction until official patches are available.
Description
idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/userLevel_deal.php?mudi=del