CVE-2024-24716

Awesome Support <= 6.1.6 - Insufficient Authorization via wpas_can_delete_attachments()

Strategic Overview

Status
Patched in 6.1.7
Affected Version
<= 6.1.6
CVSS
4.3Medium
Weakness type
CWE-863 · Incorrect Authorization
CVE
CVE-2024-24716
View all Awesome Support – WordPress HelpDesk & Support Plugin vulnerabilities

At a glance

CVE-2024-24716 is a medium-severity Incorrect Authorization vulnerability in the Awesome Support WordPress plugin, affecting versions <= 6.1.6. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 6.1.7; sites on affected versions should update now. Disclosed March 2024, reported by Brandon James Roldan (tomorrowisnew).

Vulnerability Overview

The Awesome Support – WordPress HelpDesk & Support Plugin plugin for WordPress is vulnerable to unauthorized modification of data due to an insufficient capability check in the wpas_can_delete_attachments() function in all versions up to, and including 6.1.6. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete attachments.

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 interaction from a victim user.

CWE-863: Incorrect Authorization

Awesome Support <= 6.1.6 carries this weakness at wpas_can_delete_attachments(), and reaching it takes a caller who can reach the endpoint. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.

The action runs for users the code intended to exclude, with the same effect as having no check at all. For Awesome Support the fix is 6.1.7: builds <= 6.1.6 are affected, anything from 6.1.7 onward is not.

Remediation

Update to version 6.1.7, 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.7 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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