Skip to main content
CVE-2024-40329VulnerabilityPublished Updated

CVE-2024-40329: cms · n/a

Affects cmsSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 06:26 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 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 2026-10-26.

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-40329, organizations should implement the following specific measures: 1) Deploy anti-CSRF tokens on all state-changing requests, especially the /admin/softBak_deal.php?mudi=backup endpoint, to ensure requests are legitimate and initiated by authorized users. 2) Restrict access to backup functionality to trusted IP addresses or VPNs to reduce exposure. 3) Enforce strict session management and timeout policies to minimize the window of opportunity for CSRF attacks. 4) Monitor and log all administrative backup operations for unusual activity and conduct regular audits. 5) If possible, update or patch idccms once an official fix is released; meanwhile, consider disabling the vulnerable backup feature if not critical. 6) Educate administrators about the risks of CSRF and encourage cautious behavior regarding clicking unknown links or visiting untrusted websites while logged into admin panels. 7) Employ Web Application Firewalls (WAFs) with CSRF detection capabilities to block suspicious requests. These targeted actions go beyond generic advice and directly address the vulnerability's exploitation vector.

Description

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

References

Community reviews

Loading reviews…