# CVE-2026-94246: Wallet System for WooCommerce 2.0.0 - 2.7.10 - Subscriber+ Forged Wallet Withdrawal Request via IDOR

> Authenticated users can forge withdrawal requests against other users' wallets, modifying data and blocking legitimate withdrawals.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-cgxq-x82m-q3wm

## What is CVE-2026-94246?

CVE-2026-94246 is a medium-severity missing authorization vulnerability in Unknown Wallet System for WooCommerce, published on 8 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The Wallet System for WooCommerce  WordPress plugin before 2.8.0 does not verify that the wallet account named in a withdrawal submission belongs to the user making it, allowing any authenticated user, such as a subscriber, to file a withdrawal request against another user's wallet for an amount and a payout destination of their choosing, and to indefinitely prevent that user from submitting withdrawals of their own.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-94246 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94246 is a medium-severity missing authorization vulnerability in Unknown Wallet System for WooCommerce, published on 8 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-94246 in the wild and no public exploit code.

Affected product: Unknown Wallet System for WooCommerce. 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-94246/ (Markdown: https://insights.sbomify.com/CVE-2026-94246/index.md)
```

## Sources

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

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