Skip to main content
CVE-2024-42612VulnerabilityPublished Updated

CVE-2024-42612: cms2 · n/a

Affects cms2Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 06:26 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-26.

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-42612, organizations should implement the following specific measures: 1) Immediately restrict access to the /admin/domain_management.php endpoint to trusted IP addresses or VPNs to reduce exposure. 2) Employ anti-CSRF tokens in all administrative forms and verify their presence server-side to prevent unauthorized requests. 3) 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. 4) Monitor web server and application logs for unusual POST requests to the vulnerable endpoint. 5) If possible, temporarily disable the domain whitelist management feature until a patch is released. 6) Keep the CMS and all related components updated and subscribe to vendor or community advisories for timely patch releases. 7) Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block CSRF attack patterns targeting this endpoint. These targeted actions go beyond generic advice and address the specific nature of this vulnerability.

Description

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

References

Community reviews

Loading reviews…