CVE-2024-42617: cms2 · n/a
Affects cms2Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 06:26 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-26.
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-42617, organizations should implement the following specific measures: 1) Immediately restrict administrative access to trusted networks and IP addresses to reduce exposure. 2) Employ web application firewalls (WAFs) with custom rules to detect and block suspicious requests targeting /admin/admin_config.php with the vulnerable parameters. 3) Educate administrators on the risks of CSRF and advise against clicking unknown or untrusted links while logged into the CMS. 4) Implement multi-factor authentication (MFA) for admin accounts to reduce the risk of session hijacking. 5) Monitor administrative logs for unusual configuration changes or access patterns. 6) If possible, temporarily disable or restrict the vulnerable functionality until an official patch is released. 7) Follow the Pligg CMS community and security advisories closely for updates or patches addressing this vulnerability. 8) Consider deploying Content Security Policy (CSP) headers to limit the execution of unauthorized scripts that could facilitate CSRF attacks. These targeted actions go beyond generic advice and help reduce the risk of exploitation in the absence of an official patch.
Description
Pligg CMS v2.0.2 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/admin_config.php?action=save&var_id=32