Skip to main content
VulnerabilityPublished Updated

CVE-2024-40333: cms · Cross-site Scripting

Affects cmsSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
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: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-40333, organizations should first check for any official patches or updates from the idccms vendor and apply them promptly once available. In the absence of patches, implement anti-CSRF tokens in all state-changing requests, especially those involving administrative actions like deletion. Restrict access to the /admin/softBak_deal.php endpoint by IP whitelisting or VPN-only access to reduce exposure. Enforce strict session management policies, including short session timeouts and re-authentication for sensitive actions. Educate administrators about the risks of CSRF and the importance of not clicking on suspicious links or visiting untrusted websites while logged into the CMS. Employ web application firewalls (WAFs) with rules to detect and block CSRF attack patterns targeting the vulnerable endpoint. Regularly monitor logs for unusual administrative requests or patterns indicating potential exploitation attempts. Finally, consider isolating the CMS administrative interface from the public internet where feasible to minimize attack surface.

Description

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

References

Community reviews

Loading reviews…