Skip to main content
CVE-2024-39022VulnerabilityPublished Updated

CVE-2024-39022: cms2 · n/a

Affects cms2Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 07:57 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 22% 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 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-39022, organizations should immediately implement the following specific measures: 1) Apply CSRF tokens to all state-changing requests in the admin interface, ensuring that each request includes a unique, unpredictable token validated server-side. 2) Enforce strict referer and origin header checks to verify that requests originate from trusted sources. 3) Restrict access to the /admin/infoSys_deal.php endpoint by IP whitelisting or VPN-only access to reduce exposure. 4) Implement multi-factor authentication (MFA) for administrative accounts to reduce the risk of session hijacking. 5) Monitor web server logs for unusual or suspicious POST requests targeting the vulnerable endpoint. 6) Educate administrators about phishing and social engineering risks to prevent inadvertent interaction with malicious links. 7) If possible, upgrade to a patched or newer version of idccms once available. 8) Employ Web Application Firewalls (WAFs) with custom rules to detect and block CSRF attack patterns targeting this endpoint. These targeted mitigations go beyond generic advice by focusing on the specific vulnerable endpoint and attack vector.

Description

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

References

Community reviews

Loading reviews…