Skip to main content
CVE-2024-42604VulnerabilityPublished Updated

CVE-2024-42604: cms2 · n/a

Affects cms2Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 25 Oct 2026, 19:02 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 2026-10-25.

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-42604 effectively, organizations should immediately implement the following measures: 1) Restrict administrative access to trusted networks and IP addresses to reduce exposure. 2) Educate administrators about the risks of CSRF and the importance of avoiding clicking on suspicious links or visiting untrusted websites while logged into the CMS. 3) Employ web application firewalls (WAFs) with rules designed to detect and block suspicious requests targeting /admin/admin_group.php with delete parameters. 4) If possible, apply custom patches or temporary code modifications to enforce anti-CSRF tokens on the vulnerable endpoint until an official patch is released. 5) Monitor administrative logs for unusual group deletion activities to detect potential exploitation attempts. 6) Regularly back up CMS data and configurations to enable recovery from unauthorized changes. 7) Follow updates from Pligg CMS developers and apply official security patches as soon as they become available. 8) Consider isolating the CMS environment or using multi-factor authentication for administrative accounts to add additional security layers.

Description

Pligg CMS v2.0.2 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/admin_group.php?mode=delete&group_id=3

References

Community reviews

Loading reviews…