CVE-2026-16605
HighCVSS 7.2Exploitation Probability (EPSS)
Low risk24th percentile - higher than 24% of all known CVEs
Summary
The MultiVendorX WordPress plugin before 5.0.11 does not verify that the store targeted through its REST API belongs to the requesting vendor, allowing an authenticated vendor (Store Owner and above) to view, take over, permanently delete, or modify any other vendor's store on the marketplace.
Risk Assessment
The vulnerability allows full account takeover of another vendor, deletion of their store, or modification of data, potentially leading to significant financial losses and loss of trust on the platform.
Recommendation
Immediately update the plugin to version 5.0.11 or later and implement additional access controls in the REST API.
Other vulnerabilities in MultiVendorX
See all- CVE-2026-66651Medium
Broken Access Control vulnerability in MultiVendorX versions up to 5.0.14. The attack does not require authentication.
- CVE-2026-66441High
Unauthenticated Broken Access Control vulnerability in MultiVendorX versions up to 5.0.10.
- CVE-2026-16746Low
The MultiVendorX WordPress plugin before 5.0.11 does not verify that the requested store belongs to the current user in one of its REST API endpoints, allowing any vendor-level user to read other vendors' commission and financial data.
- CVE-2026-12941Medium
The MultiVendorX plugin for WordPress is vulnerable to generic SQL injection via the 'order_by' parameter in versions up to and including 5.0.9. Insufficient escaping and lack of proper SQL query preparation allow authenticated attackers with subscriber-level access or higher to append additional SQL queries.
Original NVD description (English source)
The MultiVendorX WordPress plugin before 5.0.11 does not verify that the store targeted through its REST API belongs to the requesting vendor, allowing an authenticated vendor (Store Owner and above) to view, take over, permanently delete, or modify any other vendor's store on the marketplace.