CVE-2024-42619: cms2 · Cross-Site Request Forgery (CSRF)
Affects cms2Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 17% 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 26 Oct 2026.
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-42619 effectively, organizations should implement the following specific measures: 1) Restrict access to the /admin/domain_management.php endpoint by IP whitelisting or VPN-only access to reduce exposure to unauthorized requests. 2) Employ web application firewalls (WAFs) with custom rules to detect and block suspicious CSRF-like requests targeting the vulnerable endpoint. 3) Educate administrators to avoid clicking on untrusted links or visiting unknown websites while logged into the CMS admin panel to reduce the risk of user interaction-based exploitation. 4) Implement browser security features such as SameSite cookies to limit cross-origin request capabilities. 5) Monitor logs for unusual changes to domain whitelist configurations or unexpected admin actions. 6) If possible, apply manual code-level mitigations by adding anti-CSRF tokens or validating the HTTP Referer header in the affected script until an official patch is released. 7) Regularly back up CMS configurations and data to enable quick recovery in case of compromise. 8) Stay informed about updates from Pligg CMS developers and apply patches promptly once available.
Description
Pligg CMS v2.0.2 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/domain_management.php?id=0&list=whitelist&remove=pligg.com