Skip to main content
CVE-2024-39019VulnerabilityPublished Updated

CVE-2024-39019: cms2 · n/a

Affects cms2Source CVE Database V5

0

Not known to be exploited · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 9% 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:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 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
GitHubda271133/cms2pkg:github/da271133/cms2Other 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-39019, organizations should implement the following specific measures: 1) Apply CSRF tokens to all state-changing requests, especially the /admin/idcProData_deal.php endpoint, ensuring tokens are validated server-side. 2) Enforce strict origin and referer header checks to verify that requests originate from trusted sources. 3) Restrict administrative interface access by IP whitelisting or VPN to reduce exposure. 4) Educate administrators about phishing and social engineering risks to minimize the chance of interacting with malicious links. 5) Monitor logs for unusual deletion requests or patterns indicating CSRF exploitation attempts. 6) If possible, temporarily disable or restrict the vulnerable functionality until an official patch is released. 7) Engage with the vendor or community to obtain or develop patches addressing this vulnerability. 8) Implement Content Security Policy (CSP) headers to reduce the risk of malicious script execution that could facilitate CSRF attacks. These targeted actions go beyond generic advice and focus on reducing the attack surface and preventing unauthorized state changes.

Description

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

References

Community reviews

Loading reviews…