CVE-2024-42617: 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_config.php?action=save&var_id=32
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-42617?
The severity of CVE-2024-42617 is considered to be high due to its potential impact on the security of the Pligg CMS.
How do I fix CVE-2024-42617?
To fix CVE-2024-42617, update Pligg CMS to the latest version that addresses this CSRF vulnerability.
What type of vulnerability is CVE-2024-42617?
CVE-2024-42617 is a Cross-Site Request Forgery (CSRF) vulnerability affecting Pligg CMS.
Is my site vulnerable if I use Pligg CMS 2.0.2?
Yes, if you are using Pligg CMS version 2.0.2, your site is vulnerable to CVE-2024-42617.
What can attackers do with CVE-2024-42617?
Attackers exploiting CVE-2024-42617 could perform unauthorized actions on behalf of an authenticated user, compromising site security.
- 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