CVE-2026-15351
MediumCVSS 4.9Exploitation Probability (EPSS)
Low risk21th percentile - higher than 21% of all known CVEs
Summary
The WC Vendors plugin for WordPress up to version 2.7.0 is vulnerable to generic SQL Injection via the 'status' parameter. Insufficient escaping and lack of query preparation allow authenticated attackers with shop manager-level access and above to append additional SQL queries, potentially extracting sensitive information from the database.
Risk Assessment
An attacker can access confidential database information such as customer data, passwords, or payment details, potentially leading to privacy breaches and legal consequences.
Recommendation
Update the WC Vendors plugin to the latest patched version. Restrict administrative functions to trusted users only.
Other vulnerabilities in WC Vendors
See all- CVE-2026-81428Medium
The WC Vendors WordPress plugin before 2.7.2.1 does not verify ownership or the object type of user-supplied IDs when saving product variations, allowing authenticated users with the vendor role to modify product variations belonging to other vendors, and to change the status and title of arbitrary posts, via IDOR.
- CVE-2026-81427Medium
The WC Vendors WordPress plugin before 2.7.2.1 does not verify that the vendor submitting a front-end order shipment status change owns the referenced order, allowing any authenticated vendor to mark another vendor's order as shipped, add an order note falsely attributed to the victim vendor, and trigger the customer shipment notification email.
- CVE-2026-81426Medium
The WC Vendors WordPress plugin before 2.7.2.1 does not have CSRF protection on some of its front-end order shipment status actions, which could allow attackers to make a logged-in vendor change the shipment status of their own orders via a crafted request.
Original NVD description (English source)
The WC Vendors – WooCommerce Multivendor, WooCommerce Marketplace, Product Vendors plugin for WordPress is vulnerable to generic SQL Injection via the 'status' parameter in all versions up to, and including, 2.7.0 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 shop manager-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The sanitize_text_field callback strips HTML but leaves SQL metacharacters intact, and wp_magic_quotes slash protection does not apply because WP_REST_Server::serve_request() calls wp_unslash() on GET parameters before the sanitize callback executes.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS