EUVD-2026-44860
GHSA-95xv-f86p-3j6g
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Network vector via REST API, low complexity; PR:L reflects the subscriber-level account requirement even with default auto-promote path; read-only injection so I:N and A:N.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
Lifecycle Timeline
2DescriptionCVE.org
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.
AnalysisAI
SQL injection in MultiVendorX (WooCommerce Multivendor Marketplace) plugin versions up to and including 5.0.9 allows any authenticated WordPress user to extract sensitive data from the database via the unparameterized 'order_by' argument in the transactions REST endpoint. Critically, the default plugin configuration automatically approves store owner registrations, meaning any subscriber-level WordPress account holder can self-elevate to store_owner role via the public Stores REST endpoint, then immediately exploit the injection - effectively lowering the real-world privilege bar to any authenticated user. No public exploit code or CISA KEV listing has been identified at time of analysis, but the default-on privilege escalation path substantially raises exploitability beyond the PR:L CVSS score suggests.
Technical ContextAI
MultiVendorX is a WooCommerce extension that transforms WordPress sites into multivendor marketplaces. The affected code resides in two REST API controller files: classes/RestAPI/Controllers/Transactions.php (lines 76 and 113) and the underlying classes/Transaction/Transaction.php (line 274), as confirmed by the WordPress plugin trac source references. The root cause is CWE-89 (Improper Neutralization of Special Elements used in an SQL Command): the 'order_by' parameter passed to the transactions query is interpolated directly into the SQL ORDER BY clause without use of WordPress's $wpdb->prepare() or equivalent escaping, permitting UNION-based or stacked query injection to read arbitrary tables. The CPE string cpe:2.3:a:wcmp:multivendorx_-_woocommerce_multivendor_marketplace_ai_powered_solutions:*:*:*:*:*:*:*:* covers all versions up to 5.0.9. The secondary weakness is an insecure default: automatic store owner approval enables unauthenticated self-registration to a privileged role, widening the attack surface beyond what the CVSS PR:L metric captures.
RemediationAI
The upstream fix has been committed to the WordPress plugin repository as changeset 3606843 (https://plugins.trac.wordpress.org/changeset?reponame=&old=3606843%40dc-woocommerce-multi-vendor&new=3606843%40dc-woocommerce-multi-vendor); site administrators should update to the version released after 5.0.9 as soon as it becomes available in the WordPress plugin directory, though a specific patched release version has not been independently confirmed from the available intelligence. As an immediate compensating control, administrators should navigate to the MultiVendorX store settings and disable automatic store owner approval, requiring manual review of new vendor registrations - this eliminates the self-elevation path that effectively allows any authenticated user to reach the vulnerable endpoint, raising the real-world attack bar back to requiring a pre-existing store_owner or higher account. A secondary mitigation is to restrict access to the /wp-json/ REST API for non-administrative roles via a WAF rule or server-level block on the transactions endpoint path, though this may break legitimate vendor functionality. The Wordfence advisory at the URL above should be monitored for patch version confirmation.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
Same weakness CWE-89 – SQL Injection
View allShare
External POC / Exploit Code
Leaving vuln.today