CVE-2026-4654

Awesome Support <= 6.3.7 - Authenticated (Subscriber+) Insecure Direct Object Reference to Unauthorized Ticket Reply Access via 'ticket_id' Parameter

2026-04-07 00:00
Michael Iden (Mickhat)

Strategic Overview

Status
Patched in 6.3.8
Affected Plugin
Awesome Support – WordPress HelpDesk & Support Plugin
Affected Version
<= 6.3.7
CVSS
5.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-4654
View all Awesome Support – WordPress HelpDesk & Support Plugin vulnerabilities

At a glance

CVE-2026-4654 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Awesome Support WordPress plugin, affecting versions <= 6.3.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.3.8; sites on affected versions should update now. Disclosed April 2026, reported by Michael Iden (Mickhat).

Vulnerability Overview

The Awesome Support – WordPress HelpDesk & Support Plugin plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 6.3.7. This is due to the wpas_get_ticket_replies_ajax() function failing to verify whether the authenticated user has permission to view the specific ticket being requested. This makes it possible for authenticated attackers, with subscriber-level access and above, to access sensitive information from all support tickets in the system by manipulating the ticket_id parameter.

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-639: Authorization Bypass Through User-Controlled Key

Awesome Support <= 6.3.7 carries this weakness at wpas_get_ticket_replies_ajax(), and reaching it takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Awesome Support the fix is 6.3.8: builds <= 6.3.7 are affected, anything from 6.3.8 onward is not.

Remediation

Update to version 6.3.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.3.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-2026-4654https://www.wordfence.com/threat-intel/vulnerabilities/id/9f9015fa-b3f0-4312-8acd-02b715e26f33https://nvd.nist.gov/vuln/detail/CVE-2026-4654

Related records

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