MultiVendorX <= 4.0.25 - Improper Authorization on REST Routes via 'save_settings_permission'
Strategic Overview
- Status
- Patched in 4.0.26
- Affected Version
< 4.0.26- CVSS
- 8.6High
- Weakness type
- CWE-285 · Improper Authorization
- CVE
CVE pending
At a glance
This record tracks a high-severity Improper Authorization vulnerability in the MultiVendorX WordPress plugin, affecting versions < 4.0.26. It carries a CVSS score of 8.6 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 4.0.26; sites on affected versions should update now. Disclosed September 2023.
Vulnerability Overview
The MultiVendorX plugin for WordPress is vulnerable to unauthorized access of data, modification of data, and loss of data due to an improper capability check on the 'save_settings_permission' function for the REST routes instantiated by the 'mvx_rest_routes_react_module' function versions up to, and including, 4.0.25. This makes it possible for unauthenticated attackers to create, update, and delete vendors, retrieve sensitive information, and modify plugin settings.
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 confidentiality.
CWE-285: Improper Authorization
MultiVendorX < 4.0.26 carries this weakness at save_settings_permission, 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.0.26: builds < 4.0.26 are affected, anything from 4.0.26 onward is not.
Remediation
Update to version 4.0.26, 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.0.26 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