CVE-2024-8289

MultiVendorX – The Ultimate WooCommerce Multivendor Marketplace Solution <= 4.2.0 - Missing Authorization to Arbitrary Vendor Deletion

2024-09-03 00:00
wesley (wcraft)

Strategic Overview

Status
Patched in 4.2.1
Affected Version
<= 4.2.0
CVSS
7.5High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-8289
View all MultiVendorX – WooCommerce Multivendor Marketplace AI Powered Solutions vulnerabilities

At a glance

CVE-2024-8289 is a high-severity Missing Authorization vulnerability in the MultiVendorX WordPress plugin, affecting versions <= 4.2.0. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 4.2.1; sites on affected versions should update now. Disclosed September 2024, reported by wesley (wcraft).

Vulnerability Overview

The MultiVendorX – The Ultimate WooCommerce Multivendor Marketplace Solution plugin for WordPress is vulnerable to arbitrary vendor user deletion due to an insufficient capability check on the delete_item_permissions_check function in all versions up to, and including, 4.2.0. This makes it possible for unauthenticated attackers to delete arbitrary users with the vendor role. This can be combined with CVE-2024-8289 to delete administrator accounts.

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 integrity.

CWE-862: Missing Authorization

Reaching this weakness in MultiVendorX <= 4.2.0 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For MultiVendorX the fix is 4.2.1: builds <= 4.2.0 are affected, anything from 4.2.1 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

Related records

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