Description

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.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "4.9",
  "pubDate": "2026-08-16T06:16:50.620Z",
  "pubdate": "2026-08-16T06:16:50.620Z",
  "executiveSummary": "An SQL Injection vulnerability exists in the WC Vendors – WooCommerce Multivendor, WooCommerce Marketplace, Product Vendors plugin for WordPress in all versions up to, and including, 2.7.0. The vulnerability resides in the handling of the 'status' parameter, which lacks proper escaping and query preparation. This security flaw permits authenticated threat actors possessing shop manager-level access and above to manipulate existing database queries.\nSuccessful exploitation allows attackers to append arbitrary SQL commands to the original query execution flow. The primary impact of this vulnerability is unauthorized database access, enabling malicious actors to extract sensitive information stored within the underlying database. The risk implication is high, as compromise of database contents can lead to the exposure of confidential store data, customer details, and potentially further internal system compromise.\nExploitation requires authenticated access with specific privilege levels, specifically shop manager-level access or higher, limiting the threat surface to trusted or compromised privileged accounts. Mitigation requires proper input sanitization, strict query parameterization, and adherence to secure coding standards for database interactions within the plugin.",
  "technicalDetails": "The vulnerability is classified as a generic SQL Injection flaw affecting the WC Vendors – WooCommerce Multivendor, WooCommerce Marketplace, Product Vendors plugin for WordPress across all versions up to, and including, 2.7.0. The root cause of the vulnerability stems from insufficient escaping applied to user-supplied input combined with a lack of sufficient preparation on the existing SQL query structure within the vulnerable component.\nThe vulnerable parameter in question is the 'status' parameter. During execution, the application processes GET parameters through a specific control flow involving WordPress REST API handlers. Specifically, WP_REST_Server::serve_request() invokes wp_unslash() on incoming GET parameters prior to the execution of the sanitize callback. Consequently, the sanitize_text_field callback is utilized, which effectively strips HTML markup but leaves critical SQL metacharacters entirely intact. Furthermore, because wp_unslash() strips the slash protection provided by wp_magic_quotes, the input reaches the database query layer without adequate neutralization.\nThe attack flow proceeds as follows: 1) An authenticated attacker with shop manager-level access or higher crafts an HTTP request containing malicious SQL payloads injected into the 'status' parameter. 2) The WordPress REST API processes the request, invoking WP_REST_Server::serve_request() which unslashes the parameter. 3) The sanitize_text_field function executes, removing HTML while preserving SQL metacharacters. 4) The unsanitized and unparameterized input is concatenated directly into the active SQL query. 5) The database executes the modified query, allowing the attacker to append additional SQL commands.\nThe post-exploitation impact includes the capability to extract sensitive information from the database through techniques such as UNION-based SQL injection or error-based extraction. The attack requires network exposure to the WordPress REST API endpoint, authenticated access at the shop manager role or higher, and exploits the lack of parameterized queries and proper escaping mechanisms."
}