CVE-2024-42613: 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 /admin/admin_widgets.php?action=install&widget=akismet
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-42613?
CVE-2024-42613 is classified as a Cross-Site Request Forgery (CSRF) vulnerability which can lead to unauthorized actions performed on behalf of users.
How do I fix CVE-2024-42613?
To mitigate CVE-2024-42613, it is recommended to update Pligg CMS to a version that addresses this vulnerability or implement CSRF tokens in forms.
What versions of Pligg CMS are affected by CVE-2024-42613?
CVE-2024-42613 affects Pligg CMS version 2.0.2.
What type of attack does CVE-2024-42613 enable?
CVE-2024-42613 enables attackers to perform unauthorized actions on an affected user’s behalf due to the lack of proper CSRF protection.
Is there a public exploit available for CVE-2024-42613?
As of now, there are no known public exploits specifically documented for CVE-2024-42613, but it poses a significant security risk.
- 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