awesomesupport Awesome Support Plugin up to 6.3.7 on WordPress wpas_get_ticket_replies_ajax ticket_id authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in awesomesupport Awesome Support Plugin up to 6.3.7 on WordPress. It has been classified as problematic. This affects the function wpas_get_ticket_replies_ajax. The manipulation of the argument ticket_id leads to authorization.
This vulnerability is traded as CVE-2026-4654. It is possible to initiate the attack remotely. There is no exploit available.
Upgrading the affected component is recommended.
Details
A vulnerability was found in awesomesupport Awesome Support Plugin up to 6.3.7 on WordPress. It has been rated as problematic. This issue affects the function wpas_get_ticket_replies_ajax. The manipulation of the argument ticket_id with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. Impacted is confidentiality. The summary by CVE is:
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.
The weakness was shared by Michael Iden. It is possible to read the advisory at wordfence.com. The identification of this vulnerability is CVE-2026-4654 since 03/23/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 6.3.7 eliminates this vulnerability.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.3
CNA Vector (Wordfence): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-639 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Awesome Support Plugin 6.3.7
Timeline
03/23/2026 CVE reserved04/08/2026 Advisory disclosed
04/08/2026 VulDB entry created
04/08/2026 VulDB entry last update
Sources
Advisory: wordfence.comResearcher: Michael Iden
Status: Confirmed
CVE: CVE-2026-4654 (🔒)
GCVE (CVE): GCVE-0-2026-4654
GCVE (VulDB): GCVE-100-356039
Entry
Created: 04/08/2026 10:36Changes: 04/08/2026 10:36 (67)
Complete: 🔍
Cache ID: 216:A08:103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.