MultiVendorX – WooCommerce Multivendor Marketplace AI Powered Solutions: SQL injection
MultiVendorX – WooCommerce Multivendor Marketplace AI Powered Solutions is affected by SQL injection. Exploitation requires at least subscriber-level access. A successful request can alter database queries and expose or modify WordPress data. The published affected range is <= 5.0.9.
- Component
- MultiVendorX – WooCommerce Multivendor Marketplace AI Powered Solutions
- Plugin slug
dc-woocommerce-multi-vendor- Affected
- <= 5.0.9
- Safe version
> 5.0.9- Published
- Jul 16, 2026
This CVE was published Jul 16, 2026 and is one of 16 known issues for this plugin.
Update, patch or deactivate.
Update MultiVendorX – WooCommerce Multivendor Marketplace AI Powered Solutions to a release after 5.0.9, or disable and remove it until a fixed version is available.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
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 / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N