What is the severity of CVE-2024-6022?

CVE-2024-6022 is considered a medium severity vulnerability due to the potential for attackers to exploit it via CSRF attacks on admin settings.

How do I fix CVE-2024-6022?

To fix CVE-2024-6022, update the ContentLock WordPress plugin to version 1.0.4 or later, which includes the necessary CSRF checks.

Who is affected by CVE-2024-6022?

CVE-2024-6022 affects users of the ContentLock WordPress plugin versions prior to 1.0.4.

What type of attack does CVE-2024-6022 allow?

CVE-2024-6022 allows CSRF attacks, enabling logged in attackers to change plugin settings without proper authentication.

Is there a workaround for CVE-2024-6022?

The best workaround for CVE-2024-6022 is to restrict access to the WordPress admin area and update the plugin until a patch is applied.

Vulnerability/
CVE-2024-6022

high

8.8

CWE

352

EPSS

0.058%

12/7/2024

2/8/2024

CVE-2024-6022: ContentLock <= 1.0.3 - Settings Update via CSRF

First published: Fri Jul 12 2024(Updated: )

The ContentLock WordPress plugin through 1.0.3 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack

Credit: contact@wpscan.com

Affected Software	Affected Version	How to fix
WordPress	<1.0.4

Never miss a vulnerability like this again

Reference Links

https://wpscan.com/vulnerability/871a93b5-ec67-4fe0-bc39-e5485477fbeb/

Frequently Asked Questions

What is the severity of CVE-2024-6022?
CVE-2024-6022 is considered a medium severity vulnerability due to the potential for attackers to exploit it via CSRF attacks on admin settings.
How do I fix CVE-2024-6022?
To fix CVE-2024-6022, update the ContentLock WordPress plugin to version 1.0.4 or later, which includes the necessary CSRF checks.
Who is affected by CVE-2024-6022?
CVE-2024-6022 affects users of the ContentLock WordPress plugin versions prior to 1.0.4.
What type of attack does CVE-2024-6022 allow?
CVE-2024-6022 allows CSRF attacks, enabling logged in attackers to change plugin settings without proper authentication.
Is there a workaround for CVE-2024-6022?
The best workaround for CVE-2024-6022 is to restrict access to the WordPress admin area and update the plugin until a patch is applied.

agent/references
agent/title
agent/description
agent/first-publish-date
agent/type
agent/author
collector/mitre-cve
source/MITRE
agent/weakness
agent/severity
agent/event
agent/last-modified-date
agent/softwarecombine
collector/epss-latest
source/FIRST
agent/epss
agent/source
agent/tags
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/software-canonical-lookup-request
vendor/adamsolymosi
canonical/wordpress

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-6022?
CVE-2024-6022 is considered a medium severity vulnerability due to the potential for attackers to exploit it via CSRF attacks on admin settings.
How do I fix CVE-2024-6022?
To fix CVE-2024-6022, update the ContentLock WordPress plugin to version 1.0.4 or later, which includes the necessary CSRF checks.
Who is affected by CVE-2024-6022?
CVE-2024-6022 affects users of the ContentLock WordPress plugin versions prior to 1.0.4.
What type of attack does CVE-2024-6022 allow?
CVE-2024-6022 allows CSRF attacks, enabling logged in attackers to change plugin settings without proper authentication.
Is there a workaround for CVE-2024-6022?
The best workaround for CVE-2024-6022 is to restrict access to the WordPress admin area and update the plugin until a patch is applied.