WooCommerce Products Vendor <= 2.1.65 - Insecure Direct Object Reference to Note Creation

2022-10-04 00:00
foobar7

Strategic Overview

Status
Patched in 2.1.66
Affected Plugin
Product Vendors
Affected Version
<= 2.1.65
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE pending
View all Product Vendors vulnerabilities

At a glance

This record tracks a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Product Vendors WordPress plugin, affecting versions <= 2.1.65. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 2.1.66; sites on affected versions should update now. Disclosed October 2022, reported by foobar7.

Vulnerability Overview

The WooCommerce Products Vendor plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 2.1.65. This is due to insufficient validation on the 'post_id' value supplied to the 'wc_product_vendors_vendor_add_order_note' AJAX action. This makes it possible for vendors to add notes to other vendors orders.

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

Product Vendors <= 2.1.65 carries this weakness at post_id, 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 Product Vendors the fix is 2.1.66: builds <= 2.1.65 are affected, anything from 2.1.66 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/57465fce-e8ad-41ac-9dd6-e340ec314913

Related records

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