CVE-2024-0596

Awesome Support – WordPress HelpDesk & Support Plugin <= 6.1.7 - Missing Authorization via editor_html()

2024-02-09 00:00
Krzysztof Zając

Strategic Overview

Status
Patched in 6.1.8
Affected Plugin
Awesome Support – WordPress HelpDesk & Support Plugin
Affected Version
<= 6.1.7
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-0596
View all Awesome Support – WordPress HelpDesk & Support Plugin vulnerabilities

At a glance

CVE-2024-0596 is a medium-severity Missing Authorization vulnerability in the Awesome Support WordPress plugin, affecting versions <= 6.1.7. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.1.8; sites on affected versions should update now. Disclosed February 2024, reported by Krzysztof Zając.

Vulnerability Overview

The Awesome Support – WordPress HelpDesk & Support Plugin plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the editor_html() function in all versions up to, and including, 6.1.7. This makes it possible for authenticated attackers, with subscriber-level access and above, to view password protected and draft posts. CVE-2024-35741 is likely a duplicate of this issue.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

Awesome Support <= 6.1.7 carries this weakness at editor_html(), and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Awesome Support the fix is 6.1.8: builds <= 6.1.7 are affected, anything from 6.1.8 onward is not.

Remediation

Update to version 6.1.8, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Awesome Support 6.1.8 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-0596https://www.wordfence.com/threat-intel/vulnerabilities/id/e4358e2a-b7f6-44b6-a38a-5b27cb15e1cdhttps://nvd.nist.gov/vuln/detail/CVE-2024-0596

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C