What is the severity of CVE-2024-30539?

CVE-2024-30539 is classified as a medium severity vulnerability.

How do I fix CVE-2024-30539?

To mitigate CVE-2024-30539, update the Awesome Support plugin to version 6.1.8 or later.

What are the consequences of CVE-2024-30539?

Exploitation of CVE-2024-30539 may allow unauthorized access to restricted features within the Awesome Support plugin.

Which versions of Awesome Support are affected by CVE-2024-30539?

CVE-2024-30539 affects Awesome Support versions prior to 6.1.8, including version 6.1.7.

Is there a workaround for CVE-2024-30539?

A recommended workaround for CVE-2024-30539 is to disable the Awesome Support plugin until it has been updated.

Vulnerability/
CVE-2024-30539

critical

9.8

CWE

862

9/6/2024

2/8/2024

CVE-2024-30539: WordPress Awesome Support plugin <= 6.1.7 - Broken Access Control vulnerability

First published: Sun Jun 09 2024(Updated: )

Missing Authorization vulnerability in Awesome Support Team Awesome Support.This issue affects Awesome Support: from n/a through 6.1.7.

Credit: audit@patchstack.com

Affected Software	Affected Version	How to fix
Awesome Support	<6.1.8

Remedy

Update to 6.1.8 or a higher version.

Never miss a vulnerability like this again

Reference Links

https://patchstack.com/database/vulnerability/awesome-support/wordpress-awesome-support-plugin-6-1-7-broken-access-control-vulnerability?_s_id=cve

Frequently Asked Questions

What is the severity of CVE-2024-30539?
CVE-2024-30539 is classified as a medium severity vulnerability.
How do I fix CVE-2024-30539?
To mitigate CVE-2024-30539, update the Awesome Support plugin to version 6.1.8 or later.
What are the consequences of CVE-2024-30539?
Exploitation of CVE-2024-30539 may allow unauthorized access to restricted features within the Awesome Support plugin.
Which versions of Awesome Support are affected by CVE-2024-30539?
CVE-2024-30539 affects Awesome Support versions prior to 6.1.8, including version 6.1.7.
Is there a workaround for CVE-2024-30539?
A recommended workaround for CVE-2024-30539 is to disable the Awesome Support plugin until it has been updated.

agent/remedy
agent/weakness
agent/title
agent/references
agent/description
agent/first-publish-date
agent/type
agent/author
agent/event
agent/severity
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/source
agent/tags
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/software-canonical-lookup-request
vendor/getawesomesupport
canonical/awesome support

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-30539?
CVE-2024-30539 is classified as a medium severity vulnerability.
How do I fix CVE-2024-30539?
To mitigate CVE-2024-30539, update the Awesome Support plugin to version 6.1.8 or later.
What are the consequences of CVE-2024-30539?
Exploitation of CVE-2024-30539 may allow unauthorized access to restricted features within the Awesome Support plugin.
Which versions of Awesome Support are affected by CVE-2024-30539?
CVE-2024-30539 affects Awesome Support versions prior to 6.1.8, including version 6.1.7.
Is there a workaround for CVE-2024-30539?
A recommended workaround for CVE-2024-30539 is to disable the Awesome Support plugin until it has been updated.