# CVE-2026-81427: WC Vendors < 2.7.2.1 - Vendor+ Cross-Vendor Order Shipment Status Change

> Authenticated vendors can modify other vendors' orders and trigger notifications due to missing ownership checks in WC Vendors.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-4pgf-p454-mf4w

## What is CVE-2026-81427?

CVE-2026-81427 is a medium-severity missing authorization vulnerability in Unknown WC Vendors, published on 2 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WC Vendors  WordPress plugin before 2.7.2.1 does not verify that the vendor submitting a front-end order shipment status change owns the referenced order, allowing any authenticated vendor to mark another vendor's order as shipped, add an order note falsely attributed to the victim vendor, and trigger the customer shipment notification email.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-81427 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-81427 is a medium-severity missing authorization vulnerability in Unknown WC Vendors, published on 2 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-81427 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-81427/ (Markdown: https://insights.sbomify.com/CVE-2026-81427/index.md)
```

## Sources

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

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