CVE-2022-3511

Awesome Support <= 6.1.1 - Insecure Direct Object Reference to (Subscriber+) Ticket Export

2022-11-07 00:00
dc11

Strategic Overview

Status
Patched in 6.1.2
Affected Plugin
Awesome Support – WordPress HelpDesk & Support Plugin
Affected Version
<= 6.1.1
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2022-3511
View all Awesome Support – WordPress HelpDesk & Support Plugin vulnerabilities

At a glance

CVE-2022-3511 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Awesome Support WordPress plugin, affecting versions <= 6.1.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 6.1.2; sites on affected versions should update now. Disclosed November 2022, reported by dc11.

Vulnerability Overview

The Awesome Support plugin for WordPress is vulnerable to Insecure Direct Object Reference to (Subscriber+) Ticket Export in versions up to, and including, 6.1.1. Improper protection of the 'file' parameter used to control the user id value during exported tickets archive downloads makes it possible for subscriber-level attackers to download arbitrary exported tickets for any user with tickets on the target site. These tickets could contain sensitive information.

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

Awesome Support <= 6.1.1 carries this weakness at file, and reaching it takes a caller who can reach the endpoint. 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.1.2: builds <= 6.1.1 are affected, anything from 6.1.2 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-3511https://www.wordfence.com/threat-intel/vulnerabilities/id/5a94c5e7-a3d6-435b-9d10-0c325a13124fhttps://nvd.nist.gov/vuln/detail/CVE-2022-3511

Related records

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