Skip to main content
VulnerabilityPublished

CVE-2024-42606: cms2 · Cross-Site Request Forgery (CSRF)

Affects cms2Source CVE Database V5

0

Not known to be exploited · CVSS 5.7 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
5.7Medium
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Aug 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
GitHubjinwu1234567890/cms2pkg:github/jinwu1234567890/cms2Other threatsAffected
  • =2.0.2
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 this vulnerability, organizations should implement the following specific measures: 1) Apply any available patches or updates from the Pligg CMS maintainers 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_log.php with the clear=1 parameter. 3) Enforce strict anti-CSRF tokens on all state-changing administrative actions to ensure requests originate from legitimate sources. 4) Educate administrators on phishing and social engineering risks to reduce the likelihood of user interaction enabling exploitation. 5) Restrict administrative access to trusted networks or VPNs to limit exposure. 6) Monitor logs for unusual clearing activity and implement alerting mechanisms for administrative log deletions. 7) Consider additional multi-factor authentication (MFA) for administrative accounts to reduce risk of credential misuse. These targeted actions 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_log.php?clear=1

References

Community reviews

Loading reviews…