Multivendor Marketplace Solution for WooCommerce <= 3.7.3 - Insecure Direct Object Reference

2021-05-26 00:00
WPScanTeam

Strategic Overview

Status
Patched in 3.7.4
Affected Plugin
MultiVendorX – WooCommerce Multivendor Marketplace AI Powered Solutions
Affected Version
<= 3.7.3
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE pending
View all MultiVendorX – WooCommerce Multivendor Marketplace AI Powered Solutions vulnerabilities

At a glance

This record tracks a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the MultiVendorX WordPress plugin, affecting versions <= 3.7.3. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.7.4; sites on affected versions should update now. Disclosed May 2021, reported by WPScanTeam.

Vulnerability Overview

The Multivendor Marketplace Solution for WooCommerce plugin for WordPress is vulnerable to users commenting as a different user in versions up to, and including, 3.7.3. This is due to improper user ID validation and and capability checking This makes it possible for unauthenticated attackers to post unwanted arbitrary comments as other users.

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.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in MultiVendorX <= 3.7.3 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 MultiVendorX the fix is 3.7.4: builds <= 3.7.3 are affected, anything from 3.7.4 onward is not.

Remediation

Update to version 3.7.4, 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: MultiVendorX 3.7.4 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/24f13f9a-b240-4e32-9f12-117dbe7ecac4

Related records

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