MultiVendorX – The Ultimate WooCommerce Multivendor Marketplace Solution <= 4.2.4 - Missing Authorization to Forged Vendor Profile Deletion Email Sending
Strategic Overview
- Status
- Patched in 4.2.5
- Affected Version
<= 4.2.4- CVSS
- 4.3Medium
- Weakness type
- CWE-285 · Improper Authorization
- CVE
CVE-2024-9531
At a glance
CVE-2024-9531 is a medium-severity Improper Authorization vulnerability in the MultiVendorX WordPress plugin, affecting versions <= 4.2.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 4.2.5; sites on affected versions should update now. Disclosed October 2024, reported by Tieu Pham Trong Nhan.
Vulnerability Overview
The MultiVendorX – The Ultimate WooCommerce Multivendor Marketplace Solution plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'mvx_sent_deactivation_request' function in all versions up to, and including, 4.2.4. This makes it possible for authenticated attackers, with Subscriber-level access and above, to send a canned email to the site's administrator asking to delete the profile of an arbitrary vendor.
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-285: Improper Authorization
MultiVendorX <= 4.2.4 carries this weakness at mvx_sent_deactivation_request, and reaching it takes a caller who can reach the endpoint. Improper authorization means a permission check exists but does not cover the case being exercised, so a caller who is allowed to do one thing is allowed to do a neighbouring thing as well.
A lower-privileged account performs an action reserved for a higher one, which on a multi-author or membership site means an ordinary user reaching administrative behaviour. For MultiVendorX the fix is 4.2.5: builds <= 4.2.4 are affected, anything from 4.2.5 onward is not.
Remediation
Update to version 4.2.5, 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.5 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.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 - 6.5CVE-2026-12941: MultiVendorX <= 5.0.9 SQL Injection
CVE-2026-12941
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C