CVE-2024-40334: cms · n/a
Affects cmsSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 25 Oct 2026, 19:02 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 10 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubtank992/cmspkg:github/tank992/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-40334, organizations should implement the following specific measures: 1) Apply anti-CSRF tokens to all state-changing requests, especially those in administrative interfaces like /admin/serverFile_deal.php. 2) Enforce strict validation of the HTTP Referer and Origin headers to ensure requests originate from trusted sources. 3) Restrict access to administrative endpoints by IP whitelisting or VPN-only access to reduce exposure. 4) Implement multi-factor authentication for admin accounts to reduce risk from compromised credentials. 5) Monitor web server logs for unusual or repeated requests to the vulnerable endpoint that may indicate exploitation attempts. 6) If possible, update or patch idccms to a version that addresses this vulnerability once available. 7) Educate administrators about the risks of clicking on untrusted links while logged into the CMS. 8) Use Web Application Firewalls (WAFs) to detect and block suspicious CSRF attack patterns targeting the affected endpoint. These targeted mitigations go beyond generic advice by focusing on the specific vulnerable functionality and attack vectors.
Description
idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/serverFile_deal.php?mudi=upFileDel&dataID=3