# CVE-2026-81426: WC Vendors < 2.7.2.1 - Order Shipment Status Change via CSRF

> Attackers can force logged-in vendors to change shipment statuses via CSRF, requiring an upgrade to the WC Vendors plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-w2qv-2979-p285

## What is CVE-2026-81426?

CVE-2026-81426 is a medium-severity vulnerability in Unknown WC Vendors, published on 2 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

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

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-81426?


## How do I fix CVE-2026-81426?

No fix has been published for CVE-2026-81426 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-81426 being exploited?

There is no known exploitation of CVE-2026-81426 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-81426 and fix it if it is affected.

What it is: CVE-2026-81426 is a medium-severity vulnerability in Unknown WC Vendors, published on 2 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-81426 in the wild and no public exploit code.

Affected product: Unknown WC Vendors. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-81426/ (Markdown: https://insights.sbomify.com/CVE-2026-81426/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-81426
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-81426
- OSV: https://osv.dev/vulnerability/CVE-2026-81426

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-81426/
Summaries are generated and may contain mistakes; the official description above is the record.