Skip to main content
CVE-2024-42613VulnerabilityPublished

CVE-2024-42613: cms2 · n/a

Affects cms2Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 08:30 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-42613, organizations should immediately implement the following measures: 1) Restrict administrative access to trusted networks or VPNs to reduce exposure to CSRF attacks. 2) Educate administrators about the risks of clicking untrusted links, especially while logged into the CMS. 3) Employ web application firewalls (WAFs) with custom rules to detect and block suspicious requests targeting /admin/admin_widgets.php with install actions. 4) Monitor administrative logs for unusual widget installation activities. 5) If feasible, temporarily disable the widget installation feature or restrict it to authenticated sessions with additional verification steps. 6) Follow Pligg CMS community channels for official patches or updates and apply them promptly once available. 7) Consider implementing custom CSRF tokens or other anti-CSRF mechanisms in the CMS codebase if immediate patching is not possible. These steps go beyond generic advice by focusing on access controls, user awareness, and proactive monitoring tailored to this specific vulnerability.

Description

Pligg CMS v2.0.2 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /admin/admin_widgets.php?action=install&widget=akismet

References

Community reviews

Loading reviews…