CVE-2016-10930

Support Plus Responsive Ticket System < 7.1.0 - Insecure Direct Object Reference

2016-09-20 00:00
Anonymous

Strategic Overview

Status
Patched in 7.1.0
Affected Plugin
WP Support Plus Responsive Ticket System
Affected Version
< 7.1.0
CVSS
7.5High
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2016-10930
View all WP Support Plus Responsive Ticket System vulnerabilities

At a glance

CVE-2016-10930 is a high-severity Authorization Bypass Through User-Controlled Key vulnerability in the WP Support Plus Responsive Ticket System WordPress plugin, affecting versions < 7.1.0. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 7.1.0; sites on affected versions should update now. Disclosed September 2016.

Vulnerability Overview

The wp-support-plus-responsive-ticket-system plugin before 7.1.0 for WordPress has insecure direct object reference via a ticket number.

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. A successful exploit has high impact on confidentiality.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in WP Support Plus Responsive Ticket System < 7.1.0 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 WP Support Plus Responsive Ticket System the fix is 7.1.0: builds < 7.1.0 are affected, anything from 7.1.0 onward is not.

Remediation

Update to version 7.1.0, 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: WP Support Plus Responsive Ticket System 7.1.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2016-10930https://www.wordfence.com/threat-intel/vulnerabilities/id/59da86c4-1a68-4077-8b56-9c6c8afe26adhttps://nvd.nist.gov/vuln/detail/CVE-2016-10930

Related records

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