CVE-2024-42618: CSRF
First published: Tue Aug 20 2024(Updated: )
Pligg CMS v2.0.2 was discovered to contain a Cross-Site Request Forgery (CSRF) vulnerability via /module.php?module=karma
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Pligg CMS | =2.0.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2024-42618?
CVE-2024-42618 is classified as a high-severity Cross-Site Request Forgery (CSRF) vulnerability.
How does CVE-2024-42618 affect Pligg CMS?
CVE-2024-42618 allows attackers to exploit vulnerable installations of Pligg CMS v2.0.2 via unauthorized actions performed without user consent.
How do I fix CVE-2024-42618?
To mitigate CVE-2024-42618, users should upgrade to the latest version of Pligg CMS that addresses this CSRF vulnerability.
What versions of Pligg CMS are affected by CVE-2024-42618?
CVE-2024-42618 specifically affects Pligg CMS version 2.0.2.
Is CVE-2024-42618 exploitable without user interaction?
Yes, CVE-2024-42618 can be exploited by attackers remotely, without requiring direct user interaction.
- agent/references
- agent/type
- agent/description
- agent/first-publish-date
- agent/author
- agent/severity
- agent/event
- agent/last-modified-date
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/source
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/pligg
- canonical/pligg cms
- version/pligg cms/2.0.2