CVE-2024-42608: cms2 · n/a
Affects cms2Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 07:57 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-42608, organizations should implement the following specific measures: 1) Apply any available patches or updates from Pligg CMS developers as soon as they are released; monitor official channels for updates. 2) If patches are not yet available, implement web application firewall (WAF) rules to detect and block suspicious POST requests to /admin/submit_page.php that lack valid CSRF tokens or originate from untrusted sources. 3) Enforce strict anti-CSRF tokens in all administrative forms and verify their presence server-side to prevent unauthorized requests. 4) Restrict administrative access to trusted IP addresses or VPNs to reduce exposure. 5) Educate administrators about phishing risks and advise them not to click on suspicious links while logged into the CMS. 6) Monitor server and application logs for unusual administrative actions or repeated requests to the vulnerable endpoint. 7) Consider deploying multi-factor authentication (MFA) for administrative accounts to add an additional security layer. 8) Regularly back up CMS data and configurations to enable recovery in case of compromise. These targeted steps 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/submit_page.php.