CVE-2025-4101

MultiVendorX – WooCommerce Multivendor Marketplace Solutions <= 4.2.22 - Incorrect Authorization to Authenticated (Contributor+) Arbitrary Post Deletion

Strategic Overview

Status
Patched in 4.2.23
Affected Version
<= 4.2.22
CVSS
4.3Medium
Weakness type
CWE-863 · Incorrect Authorization
CVE
CVE-2025-4101
View all MultiVendorX – WooCommerce Multivendor Marketplace AI Powered Solutions vulnerabilities

At a glance

CVE-2025-4101 is a medium-severity Incorrect Authorization vulnerability in the MultiVendorX WordPress plugin, affecting versions <= 4.2.22. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 4.2.23; sites on affected versions should update now. Disclosed May 2025, reported by Brian Sans-Souci (liardom).

Vulnerability Overview

The MultiVendorX – WooCommerce Multivendor Marketplace Solutions plugin for WordPress is vulnerable to unauthorized loss of data due to a misconfigured capability check on the 'delete_fpm_product' function in all versions up to, and including, 4.2.22. This makes it possible for authenticated attackers, with Contributor-level access and above, to delete arbitrary posts, pages, attachments, and products. The vulnerability was partially patched in version 4.2.22.

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-863: Incorrect Authorization

MultiVendorX <= 4.2.22 carries this weakness at delete_fpm_product, and reaching it takes an account at Contributor level or above. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.

The action runs for users the code intended to exclude, with the same effect as having no check at all. For MultiVendorX the fix is 4.2.23: builds <= 4.2.22 are affected, anything from 4.2.23 onward is not.

Remediation

Update to version 4.2.23, 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.23 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