CVE-2024-42610: 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, 17:16 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 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-42610, organizations should implement several specific measures beyond generic advice: 1) Immediately restrict access to the /admin/admin_backup.php endpoint by IP whitelisting or VPN-only access to limit exposure to trusted administrators. 2) Implement or enforce anti-CSRF tokens in all state-changing requests within the CMS, particularly for backup operations, to ensure requests originate from legitimate sources. 3) Educate administrators about the risks of CSRF and the importance of avoiding clicking on suspicious links or visiting untrusted websites while logged into the CMS. 4) Monitor web server logs for unusual or repeated requests to the backup endpoint that could indicate exploitation attempts. 5) If possible, disable automatic or on-demand backup features temporarily until a patch or update is available. 6) Regularly update and patch Pligg CMS once a vendor fix is released to address this vulnerability. 7) Employ web application firewalls (WAFs) with custom rules to detect and block suspicious requests targeting the backup URL. These targeted mitigations will reduce the risk of exploitation and protect sensitive CMS data.
Description
Pligg CMS v2.0.2 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/admin_backup.php?dobackup=files