CVE-2024-42618: cms2 · n/a
Affects cms2Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 25 Oct 2026, 19:02 UTC
- 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:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Aug 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
GitHubjinwu1234567890/cms2pkg:github/jinwu1234567890/cms2Other threats | Affected
| 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-42618, organizations should implement the following specific measures: 1) Immediately apply any available patches or updates from Pligg CMS developers once released. 2) If patches are not yet available, implement web application firewall (WAF) rules to detect and block suspicious requests targeting /module.php?module=karma, especially those lacking valid CSRF tokens or originating from untrusted sources. 3) Enforce strict CSRF protection by adding anti-CSRF tokens to all state-changing requests in the karma module and validate them server-side. 4) Educate users and administrators about the risks of clicking unknown or suspicious links to reduce the likelihood of social engineering exploitation. 5) Monitor web server logs for unusual or repeated requests to the vulnerable endpoint that could indicate attempted exploitation. 6) Consider restricting access to the karma module endpoint to trusted IP ranges or authenticated users with multi-factor authentication to reduce exposure. 7) Conduct security assessments and penetration testing focused on CSRF vulnerabilities in the CMS environment. These targeted actions go beyond generic advice and address the specific attack vector and context of this vulnerability.
Description
Pligg CMS v2.0.2 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /module.php?module=karma