What is the severity of CVE-2024-42612?

CVE-2024-42612 is considered a moderate severity Cross-Site Request Forgery vulnerability affecting Pligg CMS v2.0.2.

How do I fix CVE-2024-42612?

To fix CVE-2024-42612, update to the latest version of Pligg CMS or implement CSRF protection measures in your application.

What is affected by CVE-2024-42612?

CVE-2024-42612 affects Pligg CMS version 2.0.2 specifically regarding the domain management functionality.

What type of attack does CVE-2024-42612 enable?

CVE-2024-42612 enables Cross-Site Request Forgery attacks, potentially allowing unauthorized actions on behalf of authenticated users.

How can CVE-2024-42612 impact users?

CVE-2024-42612 can impact users by allowing attackers to gain access to sensitive data or perform actions without user consent.

Vulnerability/
CVE-2024-42612

high

8.8

CWE

352

20/8/2024

21/8/2024

CVE-2024-42612: 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/domain_management.php?whitelist_add

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Plikli CMS

Never miss a vulnerability like this again

Reference Links

https://github.com/jinwu1234567890/cms2/tree/main/5/readme.md

Frequently Asked Questions

What is the severity of CVE-2024-42612?
CVE-2024-42612 is considered a moderate severity Cross-Site Request Forgery vulnerability affecting Pligg CMS v2.0.2.
How do I fix CVE-2024-42612?
To fix CVE-2024-42612, update to the latest version of Pligg CMS or implement CSRF protection measures in your application.
What is affected by CVE-2024-42612?
CVE-2024-42612 affects Pligg CMS version 2.0.2 specifically regarding the domain management functionality.
What type of attack does CVE-2024-42612 enable?
CVE-2024-42612 enables Cross-Site Request Forgery attacks, potentially allowing unauthorized actions on behalf of authenticated users.
How can CVE-2024-42612 impact users?
CVE-2024-42612 can impact users by allowing attackers to gain access to sensitive data or perform actions without user consent.

agent/references
agent/description
agent/first-publish-date
agent/type
agent/author
collector/nvd-api
source/NVD
agent/severity
agent/last-modified-date
agent/event
collector/mitre-cve
source/MITRE
agent/weakness
agent/source
agent/tags
agent/guess-ai
agent/software-canonical-lookup
agent/software-canonical-lookup-request
agent/softwarecombine
vendor/pligg
canonical/plikli cms

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2024-42612?
CVE-2024-42612 is considered a moderate severity Cross-Site Request Forgery vulnerability affecting Pligg CMS v2.0.2.
How do I fix CVE-2024-42612?
To fix CVE-2024-42612, update to the latest version of Pligg CMS or implement CSRF protection measures in your application.
What is affected by CVE-2024-42612?
CVE-2024-42612 affects Pligg CMS version 2.0.2 specifically regarding the domain management functionality.
What type of attack does CVE-2024-42612 enable?
CVE-2024-42612 enables Cross-Site Request Forgery attacks, potentially allowing unauthorized actions on behalf of authenticated users.
How can CVE-2024-42612 impact users?
CVE-2024-42612 can impact users by allowing attackers to gain access to sensitive data or perform actions without user consent.