MultiVendorX <= 5.0.10 - Insecure Direct Object Reference to Authenticated (Store Owner+) Cross-Store Commission Data Disclosure
Strategic Overview
- Status
- Patched in 5.0.11
- Affected Version
<= 5.0.10- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-16746
At a glance
CVE-2026-16746 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the MultiVendorX WordPress plugin, affecting versions <= 5.0.10. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Store Owner level or above. The issue is fixed in version 5.0.11; sites on affected versions should update now. Disclosed July 2026, reported by Ryan Fabella.
Vulnerability Overview
The MultiVendorX plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 5.0.10. This is due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with store owner-level access and above, to perform an unauthorized action.
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
Reaching this weakness in MultiVendorX <= 5.0.10 takes an account at Store Owner level or above. 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 5.0.11: builds <= 5.0.10 are affected, anything from 5.0.11 onward is not.
Remediation
Update to version 5.0.11, 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 5.0.11 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in MultiVendorX – WooCommerce Multivendor Marketplace AI Powered Solutions
- 9.8CVE-2025-0493: MultiVendorX Limited LFI
CVE-2025-0493 - 9.8CVE-2024-8289: MultiVendorX Limited Vendor Privilege
CVE-2024-8289 - 8.8CVE-2022-2657: Multivendor Marketplace Solution… CSRF
CVE-2022-2657 - 8.6CVE-2024-24703: MultiVendorX Marketplace Missing Authorization
CVE-2024-24703 - 8.6MultiVendorX <= 4.0.25 Improper Authorization on REST Routes
- 8.2Multivendor Marketplace Solution for WooCommerce – WC Marketplace LFI
- 7.5CVE-2024-8289: MultiVendorX Arbitrary Vendor Deletion
CVE-2024-8289 - 7.5CVE-2023-51355: WC Marketplace <= 4.0.23 Missing Authorization
CVE-2023-51355
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C