Skip to main content
VulnerabilityPublished Updated

CVE-2024-40331: cms · Cross-Site Request Forgery (CSRF)

Affects cmsSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Jul 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
GitHubtank992/cmspkg:github/tank992/cmsOther threatsAffected
  • =1.35
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-40331, 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 available, implement anti-CSRF tokens on all administrative endpoints, especially those handling critical operations like database backups, to ensure requests are legitimate. 3) Restrict access to the /admin/dbBakMySQL_deal.php endpoint by IP whitelisting or VPN-only access to reduce exposure. 4) Employ web application firewalls (WAFs) with custom rules to detect and block suspicious CSRF attempts targeting the backup endpoint. 5) Educate administrators about the risks of clicking unknown links or visiting untrusted websites while logged into the CMS. 6) Monitor logs and alerts for unusual backup operations or access patterns to detect potential exploitation attempts early. 7) Consider implementing multi-factor authentication (MFA) for administrative access to add an additional security layer. 8) Regularly review and audit administrative privileges and session management to minimize the risk of session hijacking or misuse. These targeted mitigations 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) vulnerability via /admin/dbBakMySQL_deal.php?mudi=backup

References

Community reviews

Loading reviews…