Skip to main content
CVE-2024-39157VulnerabilityPublished Updated

CVE-2024-39157: cms2 · n/a

Affects cms2Source CVE Database V5

0

Not known to be exploited · CVSS 3.8 Low.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
3.8Low
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:H/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Jun 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
GitHubthirtypenny77/cms2pkg:github/thirtypenny77/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-39157, organizations should implement robust anti-CSRF protections such as synchronizer tokens or double-submit cookies on all state-changing administrative endpoints, especially /admin/ipRecord_deal.php. Applying strict referer or origin header validation can provide additional defense layers. Limiting administrative access to trusted networks or VPNs reduces exposure. Enforcing multi-factor authentication (MFA) for administrative accounts can mitigate risks from compromised credentials. Regularly auditing and monitoring administrative actions and logs can help detect suspicious activities. If an official patch becomes available, it should be applied promptly. In the absence of patches, consider temporarily disabling or restricting access to vulnerable endpoints. Educating administrators about the risks of CSRF and encouraging safe browsing practices can reduce the likelihood of exploitation. Finally, employing web application firewalls (WAFs) with CSRF detection rules may provide an additional security layer.

Description

idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component /admin/ipRecord_deal.php?mudi=del&dataType=&dataID=1.

References

Community reviews

Loading reviews…