CVE-2024-42607: 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-42607, organizations should implement the following specific measures: 1) Apply any available patches or updates from Pligg CMS vendors as soon as they are released. 2) If patches are not yet available, implement anti-CSRF tokens on the /admin/admin_backup.php endpoint to validate legitimate requests. 3) Restrict access to the administrative interface by IP whitelisting or VPN-only access to reduce exposure. 4) Educate administrators about phishing risks and the dangers of clicking unknown links while logged into the CMS. 5) Monitor web server logs for unusual requests to the backup endpoint and audit backup operations regularly. 6) Employ Content Security Policy (CSP) headers to limit the ability of malicious sites to execute scripts or send forged requests. 7) Consider disabling or restricting the backup functionality temporarily if it is not critical. These targeted mitigations go beyond generic advice by focusing on the specific vulnerable endpoint and attack vector.
Description
Pligg CMS v2.0.2 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/admin_backup.php?dobackup=database