# CVE-2026-81426: WC Vendors WordPress plugin CSRF in order shipment status

Source: https://junglewise.ai/threats/cve-2026-81426-wc-vendors-wordpress-plugin-csrf-in-order-shipment-status  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-02. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-81426 · Severity: medium · CVSS 4.3 · Published 2026-09-02

WC Vendors is a WordPress plugin that enables multi-vendor marketplaces by allowing vendors to manage their orders and shipments. An attacker can trick a logged-in vendor into changing the shipment status of their own orders (marking them as shipped or unshipped) by directing them to a crafted URL, causing order status confusion that may disrupt customer notifications and fulfillment operations.

Technologies: [WC Vendors](https://junglewise.ai/threats/technologies/wc-vendors). Vendors: [WC Vendors](https://junglewise.ai/threats/vendors/wc-vendors).

## Quick answers

**Is CVE-2026-81426 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-81426 being exploited in the wild.

**How severe is CVE-2026-81426?** Medium severity, with a CVSS score of 4.3, published 2 September 2026.

**Which products and versions are affected?** WC Vendors before 2.7.2.1.

**Is there a fix for CVE-2026-81426?** A patch was published on 2026: fixed in version 2.7.2.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-81426 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-81426?** Check whether you run WC Vendors at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The plugin contains a cross-site request forgery (CSRF) vulnerability in its front-end order shipment status handlers (wcv_mark_shipped and wcv_mark_unshipped parameters). The handlers are triggered on page load, perform only an order-ownership check, and fail to validate CSRF tokens, allowing an attacker to forge a request that executes with the victim vendor's authentication context. The attack requires the victim to be a logged-in vendor and the attacker to know or guess a valid order ID (which are sequential and publicly visible in dashboards and customer emails). The delivery mechanism is a top-level navigation (not an embedded resource) because WordPress authentication cookies lack the SameSite attribute, defaulting to Lax behavior. The vulnerability is fixed in version 2.7.2.1.

## Affected products

- WC Vendors WC Vendors before 2.7.2.1

## Timeline

- 2026-08-31: disclosed
- 2026: patched: fixed in version 2.7.2.1

## References

- [https://wpscan.com/vulnerability/804efc9d-d2b4-46f0-a84f-0ff5fed7d3d6/](https://wpscan.com/vulnerability/804efc9d-d2b4-46f0-a84f-0ff5fed7d3d6/)

## Related threats

- [WC Vendors IDOR in product variation management](https://junglewise.ai/threats/cve-2026-81428-wc-vendors-idor-in-product-variation-management)
- [WC Vendors WordPress plugin authorization bypass in order shipment](https://junglewise.ai/threats/cve-2026-81427-wc-vendors-wordpress-plugin-authorization-bypass-in-order)