Skip to main content
VulnerabilityPublished

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

Affects cms2Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
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: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 CVE-2024-42621, organizations should take immediate and specific actions beyond generic advice: 1) Disable or restrict access to the /admin/admin_editor.php endpoint until a patch is available, especially from untrusted networks. 2) Implement or enforce CSRF protection mechanisms such as synchronizer tokens or double-submit cookies in the CMS codebase if possible. 3) Educate administrators about phishing and social engineering risks to reduce the chance of user interaction leading to exploitation. 4) Monitor administrative logs for unusual or unauthorized actions to detect potential exploitation attempts early. 5) If feasible, isolate the CMS administrative interface behind VPNs or IP whitelisting to limit exposure. 6) Regularly back up CMS data and configurations to enable rapid recovery in case of compromise. 7) Stay alert for official patches or updates from Pligg CMS maintainers and apply them promptly once released. 8) Consider migrating to alternative CMS platforms with active security support if Pligg CMS updates are not forthcoming.

Description

Pligg CMS v2.0.2 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/admin_editor.php

References

Community reviews

Loading reviews…