Skip to main content
CVE-2024-40037VulnerabilityPublished Updated

CVE-2024-40037: cms · n/a

Affects cmsSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
GitHubpangchunyuhack/cmspkg:github/pangchunyuhack/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-40037 effectively, organizations should implement multiple layers of defense beyond waiting for an official patch. First, apply strict anti-CSRF tokens on all state-changing administrative endpoints, ensuring that requests without valid tokens are rejected. Second, enforce referer header validation to confirm that requests originate from trusted sources within the application. Third, restrict administrative access by IP whitelisting or VPN-only access to reduce exposure to external attackers. Fourth, implement multi-factor authentication (MFA) for admin accounts to reduce the risk of session hijacking or credential theft. Fifth, educate administrators about phishing and social engineering risks to minimize the chance of clicking malicious links. Sixth, monitor web server logs and application behavior for unusual or unauthorized requests targeting the vulnerable endpoint. Finally, maintain regular backups of critical data to enable recovery in case of compromise. Organizations should also stay alert for official patches or updates from idccms developers and apply them promptly once available.

Description

idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/userScore_deal.php?mudi=del

References

Community reviews

Loading reviews…