Skip to main content
VulnerabilityPublished

CVE-2024-42611: 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, 14:05 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-42611 effectively, organizations should implement the following specific measures: 1) Immediately restrict access to the admin interface (admin/admin_page.php) by IP whitelisting or VPN-only access to reduce exposure. 2) Disable or limit the use of the vulnerable delete functionality until a patch is available. 3) Implement CSRF protection mechanisms such as synchronizer tokens or double-submit cookies in the CMS codebase, particularly for state-changing requests like deletions. 4) Educate administrators about the risks of clicking on untrusted links and encourage use of multi-factor authentication to reduce risk from compromised credentials. 5) Monitor web server logs for unusual or unauthorized requests targeting admin_page.php with suspicious parameters. 6) Regularly back up CMS data to enable recovery in case of successful exploitation. 7) Stay alert for official patches or updates from Pligg CMS maintainers and apply them promptly. 8) Consider deploying Web Application Firewalls (WAF) with custom rules to detect and block CSRF attack patterns targeting the affected endpoint. These targeted actions go beyond generic advice and address the specific attack vector and environment.

Description

Pligg CMS v2.0.2 was discovered to contain a Cross-Site Request Forgery (CSRF) via admin/admin_page.php?link_id=1&mode=delete

References

Community reviews

Loading reviews…