CVE-2024-42603: 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_backup.php?dobackup=clearall
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-42603?
CVE-2024-42603 has been classified as a moderate severity vulnerability due to its potential for exploitation via Cross-Site Request Forgery.
What affected software versions are vulnerable in CVE-2024-42603?
CVE-2024-42603 affects Pligg CMS version 2.0.2.
How do I fix CVE-2024-42603?
Fixing CVE-2024-42603 involves updating Pligg CMS to a patched version that addresses the CSRF vulnerability.
What exploit does CVE-2024-42603 allow?
CVE-2024-42603 allows attackers to perform unauthorized actions on behalf of authenticated users through CSRF.
Where is the vulnerability located in CVE-2024-42603?
The vulnerability in CVE-2024-42603 is located in the /admin/admin_backup.php endpoint of Pligg CMS.
- agent/references
- agent/type
- agent/description
- agent/first-publish-date
- agent/author
- agent/event
- agent/severity
- 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