CVE-2024-42603: cms2 · Cross-Site Request Forgery (CSRF)
Affects cms2Source CVE Database V5
Not known to be exploited · CVSS 5.7 Medium.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/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-42603, organizations should implement the following specific measures: 1) Apply any available patches or updates from Pligg CMS developers as soon as they are released. 2) If patches are not yet available, implement web application firewall (WAF) rules to detect and block suspicious requests targeting /admin/admin_backup.php with the dobackup=clearall parameter. 3) Enforce strict CSRF protections by ensuring that all state-changing requests require valid anti-CSRF tokens and verify the origin of requests. 4) Limit administrative access to trusted networks and use multi-factor authentication to reduce the risk of credential compromise. 5) Educate administrators about phishing and social engineering risks to prevent inadvertent execution of malicious requests. 6) Regularly back up CMS data externally and verify backup integrity to ensure recovery options remain available even if backups within the CMS are cleared. 7) Monitor logs for unusual administrative actions related to backup management to detect potential exploitation attempts early.
Description
Pligg CMS v2.0.2 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/admin_backup.php?dobackup=clearall