HomeWordPress vulnerabilitiesMultiVendorX
MultiVendorX vulnerabilities
MultiVendorX has 15 known vulnerabilities in this database. The most recent published record is dated 2 Oct 2026.
- Known vulnerabilities
- 15
- Active installs
- 2,000+
- Latest version
- 5.0.19
- Last updated
- 30 Sep 2026
- Most recent
- 2 Oct 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| SQL injection CVE-2026-12951 | Medium 6.5 | Up to 5.0.18 | Fixed in a later version (latest 5.0.19) | 5 d ago |
| Broken access control CVE-2026-74926 | High 7.1 | Before 5.0.16 | Fixed in 5.0.16 | 16 Sep 2026 |
| Privilege escalation CVE-2026-74925 | High 7.2 | Before 5.0.16 | Fixed in 5.0.16 | 11 Sep 2026 |
| Broken access control CVE-2026-74927 | Medium 5.3 | Before 5.0.15 | Fixed in 5.0.15 | 2 Sep 2026 |
| Broken access control CVE-2026-16605 | High 7.2 | Before 5.0.11 | Fixed in 5.0.11 | 5 Aug 2026 |
| Broken access control CVE-2026-16746 | Low 2.7 | Before 5.0.11 | Fixed in 5.0.11 | 5 Aug 2026 |
| SQL injection CVE-2026-12941 | Medium 6.5 | Up to 5.0.9 | Fixed in a later version (latest 5.0.19) | 16 Jul 2026 |
| Broken access control CVE-2025-4101 | Medium 4.3 | Before 4.2.23 | Fixed in 4.2.23 | 17 May 2025 |
| Broken access control CVE-2025-2789 | Medium 5.3 | Before 4.2.20 | Fixed in 4.2.20 | 5 Apr 2025 |
| File inclusion CVE-2025-0493 | Critical 9.8 | Before 4.2.15 | Fixed in 4.2.15 | 31 Jan 2025 |
| Broken access control CVE-2024-9531 | Medium 4.3 | Before 4.2.5 | Fixed in 4.2.5 | 24 Oct 2024 |
| Cross-site request forgery (CSRF) CVE-2024-9943 | Medium 6.3 | Before 4.2.5 | Fixed in 4.2.5 | 24 Oct 2024 |
| Privilege escalation CVE-2024-8289 | Critical 9.8 | Before 4.2.1 | Fixed in 4.2.1 | 4 Sep 2024 |
| Cross-site scripting (XSS) CVE-2024-5259 | Medium 6.4 | Before 4.1.12 | Fixed in 4.1.12 | 6 Jun 2024 |
| Cross-site request forgery (CSRF) CVE-2020-36741 | Medium 4.3 | Up to 3.5.7 | Fixed in a later version (latest 5.0.19) | 1 Jul 2023 |
Read the published descriptions
- CVE-2026-12951, 2 Oct 2026
- The Dc Woocommerce Multi Vendor plugin for WordPress is vulnerable to SQL Injection via the 'order_by' parameter of the /multivendorx/v1/compliance/report-abuse REST endpoint in versions up to and including 5.0.18. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query - the value is concatenated directly into an ORDER BY clause where esc_sql() (which only neutralizes characters needed to break out of quoted string literals) provides no protection. This makes it possible for authenticated attackers, with vendor-level access and above (users granted the 'edit_stores' capability), to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. CVE record
- CVE-2026-74926, 16 Sep 2026
- The MultiVendorX WordPress plugin before 5.0.16 does not verify that a user owns the store they are acting on in one of its REST API routes, allowing any authenticated user, such as a subscriber, to overwrite any store's details and payout settings and to replace the record of who owns it. CVE record
- CVE-2026-74925, 11 Sep 2026
- The MultiVendorX WordPress plugin before 5.0.16 does not restrict who can update its role and capability settings, allowing users holding its vendor role to grant that role administrator-level capabilities and take over the site. CVE record
- CVE-2026-74927, 2 Sep 2026
- The MultiVendorX WordPress plugin before 5.0.15 does not have proper authorisation controls on one of its REST API listing routes, allowing unauthenticated users to retrieve vendor contact and payout details, pending payout amounts, and administrative notes attached to store applications. CVE record
- CVE-2026-16605, 5 Aug 2026
- 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. CVE record
- CVE-2026-16746, 5 Aug 2026
- 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 record
- CVE-2026-12941, 16 Jul 2026
- The MultiVendorX - WooCommerce Multivendor Marketplace AI Powered Solutions plugin for WordPress is vulnerable to generic SQL Injection via the 'order_by' parameter in all versions up to, and including, 5.0.9 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. This vulnerability is exploitable by any authenticated subscriber-level user when the plugin's store approval setting is configured to automatically approve store owners (described as the default), as this allows any logged-in user to self-register as a store_owner via the public Stores REST endpoint, thereby obtaining the edit_stores capability required to reach the vulnerable transactions endpoint. CVE record
- CVE-2025-4101, 17 May 2025
- 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. CVE record
- CVE-2025-2789, 5 Apr 2025
- The MultiVendorX - Empower Your WooCommerce Store with a Dynamic Multivendor Marketplace - Build the Next Amazon, eBay, Etsy plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the delete_table_rate_shipping_row function in all versions up to, and including, 4.2.19. This makes it possible for unauthenticated attackers to delete Table Rates that can impact the shipping cost calculations. CVE record
- CVE-2025-0493, 31 Jan 2025
- The MultiVendorX - The Ultimate WooCommerce Multivendor Marketplace Solution plugin for WordPress is vulnerable to Limited Local File Inclusion in all versions up to, and including, 4.2.14 via the tabname parameter. This makes it possible for unauthenticated attackers to include PHP files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where PHP files can be uploaded and included CVE record
- CVE-2024-9531, 24 Oct 2024
- 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. CVE record
- CVE-2024-9943, 24 Oct 2024
- The MultiVendorX - The Ultimate WooCommerce Multivendor Marketplace Solution plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.2.4. This is due to missing or incorrect nonce validation on several functions in api/class-mvx-rest-controller.php. This makes it possible for unauthenticated attackers to update vendor account details, create vendor accounts, and delete arbitrary users via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
- CVE-2024-8289, 4 Sep 2024
- The MultiVendorX - The Ultimate WooCommerce Multivendor Marketplace Solution plugin for WordPress is vulnerable to privilege escalation/de-escalation and account takeover due to an insufficient capability check on the update_item_permissions_check and create_item_permissions_check functions in all versions up to, and including, 4.2.0. This makes it possible for unauthenticated attackers to change the password of any user with the vendor role, create new users with the vendor role, and demote other users like administrators to the vendor role. CVE record
- CVE-2024-5259, 6 Jun 2024
- The MultiVendorX Marketplace - WooCommerce MultiVendor Marketplace Solution plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘hover_animation’ parameter in all versions up to, and including, 4.1.11 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2020-36741, 1 Jul 2023
- The MultiVendorX plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.5.7. This is due to missing or incorrect nonce validation on the submit_comment() function. This makes it possible for unauthenticated attackers to submit comments via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
What to do if you run MultiVendorX
If you run MultiVendorX, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new MultiVendorX vulnerabilities
Free. We email you when a new vulnerability is published for MultiVendorX, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.