Description
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.
Published: 2026-09-02
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability occurs in the WC Vendors WordPress plugin for versions prior to 2.7.2.1, where certain front‑end actions that update the shipment status of orders lack proper CSRF protection. An attacker who can influence a logged‑in vendor user—such as by luring them to a crafted URL or embedding malicious content—can trick the vendor into submitting a request that changes an order’s status to a value chosen by the attacker. The effect is a manipulation of the vendor’s order workflow, potentially causing incorrect shipping information, customer dissatisfaction, or financial loss. This flaw is a classic CSRF weakness (CWE‑352).

Affected Systems

This flaw affects installations of the WC Vendors WordPress plugin for any application version less than 2.7.2.1. Users should verify their plugin version and apply the 2.7.2.1 update or later. All WooCommerce‑based sites using WC Vendors that have not applied the recommended patch are impacted.

Risk and Exploitability

The vulnerability is exploitable by attackers who can persuade an authenticated vendor to visit a crafted link or load a page that contains a malicious request. Because the plugin exposes state‑changing operations without token validation, the attack requires only a logged‑in session; no elevated privileges are needed beyond vendor rights. No EPSS data is available, and the flaw is not listed in the CISA KEV catalog, suggesting limited commercial exploitation to date. Nevertheless, the impact on individual vendors could be significant, and the lack of mitigations makes the attack straightforward once the target vendor is identified. Applying a patch or temporarily disabling the vulnerable functionality mitigates the risk.

Generated by OpenCVE AI on September 2, 2026 at 07:35 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the WC Vendors plugin to version 2.7.2.1 or later.
  • If an upgrade is not immediately possible, disable the front‑end shipment status change capability for vendor users until a secure fix is applied.
  • Ensure that the WordPress installation has CSRF mitigation in place, such as adding nonces to all vendor‑controlled forms or using a security plugin that enforces CSRF protection on custom endpoints.
  • Monitor vendor accounts for anomalous order status changes and consider blocking or auditing any suspicious activity.

Generated by OpenCVE AI on September 2, 2026 at 07:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 02 Sep 2026 08:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-352

Wed, 02 Sep 2026 06:15:00 +0000

Type Values Removed Values Added
Description 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.
Title WC Vendors < 2.7.2.1 - Order Shipment Status Change via CSRF
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-09-02T06:00:22.460Z

Reserved: 2026-08-26T19:11:45.522Z

Link: CVE-2026-81426

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-02T06:17:19.180

Modified: 2026-09-02T06:17:19.180

Link: CVE-2026-81426

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-02T07:45:03Z

Weaknesses
  • CWE-352

    Cross-Site Request Forgery (CSRF)