CVE-2024-40036: cms · n/a
Affects cmsSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 48% 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-40036, organizations should implement the following specific measures: 1) Immediately restrict access to the /admin/userGroup_deal.php endpoint to trusted IP addresses or VPN-only access to reduce exposure. 2) Employ anti-CSRF tokens in all state-changing requests within the CMS to ensure that requests originate from legitimate user actions. 3) Enforce strict referer header validation on administrative endpoints to detect and block unauthorized cross-origin requests. 4) Educate administrators about phishing and social engineering risks to reduce the likelihood of user interaction exploitation. 5) Monitor web server logs for suspicious requests targeting the vulnerable endpoint, especially POST requests with the specified parameters. 6) If possible, apply web application firewall (WAF) rules to detect and block CSRF attack patterns against the CMS. 7) Coordinate with the idccms vendor or community to obtain or develop patches and update to a fixed version once available. 8) Conduct regular security audits and penetration testing focusing on administrative interfaces to identify similar vulnerabilities.
Description
idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/userGroup_deal.php?mudi=add&nohrefStr=close