# CVE-2026-121993: wePOS before 2.0.3 Missing Authorization via payment/process Endpoint


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 8 Nov 2026
- **Also known as:** GHSA-7whv-72vx-cc4j

## What is CVE-2026-121993?

CVE-2026-121993 is a medium-severity vulnerability in wedevs wePOS – Point Of Sale (POS) for WooCommerce & Dokan, published on 4 Nov 2026. 

### Official description

wePOS (Point Of Sale for WooCommerce) before 2.0.3 contains a missing authorization vulnerability in the wepos/v1/payment/process REST route that allows authenticated vendor-level users to mark arbitrary orders as paid and completed by supplying another order's ID. Attackers with only the publish_shop_orders capability (such as Dokan vendor staff) can invoke the payment processing endpoint with an order ID they do not own to trigger the order completion lifecycle, including stock reduction and granting of paid-order access, without making any real payment.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-121993 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-121993 is a medium-severity vulnerability in wedevs wePOS – Point Of Sale (POS) for WooCommerce & Dokan, published on 4 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-121993 in the wild and no public exploit code.

Affected product: wedevs wePOS – Point Of Sale (POS) for WooCommerce & Dokan. 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-121993/ (Markdown: https://insights.sbomify.com/CVE-2026-121993/index.md)
```

## Sources

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

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