CVE-2023-5352

Awesome Support <= 6.1.4 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Post Modification

2023-10-16 00:00
Krzysztof Zając

Strategic Overview

Status
Patched in 6.1.5
Affected Plugin
Awesome Support – WordPress HelpDesk & Support Plugin
Affected Version
<= 6.1.4
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2023-5352
View all Awesome Support – WordPress HelpDesk & Support Plugin vulnerabilities

At a glance

CVE-2023-5352 is a medium-severity Missing Authorization vulnerability in the Awesome Support WordPress plugin, affecting versions <= 6.1.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 6.1.5; sites on affected versions should update now. Disclosed October 2023, reported by Krzysztof Zając.

Vulnerability Overview

The Awesome Support – WordPress HelpDesk & Support Plugin plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the wpas_edit_reply function in all versions up to, and including, 6.1.4. This makes it possible for authenticated attackers, with subscriber-level access and above, to modify arbitrary posts that they do not own.

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-862: Missing Authorization

Reaching this weakness in Awesome Support <= 6.1.4 takes an account at Subscriber level or above. 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.5: builds <= 6.1.4 are affected, anything from 6.1.5 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-5352https://www.wordfence.com/threat-intel/vulnerabilities/id/a162132a-f893-42fa-85f1-b42f738891a4https://nvd.nist.gov/vuln/detail/CVE-2023-5352

Related records

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