# CVE-2026-97219: MStore API 4.21.1 - 4.22.0 - Subscriber+ Payment Bypass via 'status' Parameter

> Authenticated users can bypass payment validation by modifying order status, allowing them to receive goods without paying.

- **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 Oct 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-2gpc-rx3g-g49h

## What is CVE-2026-97219?

CVE-2026-97219 is a medium-severity vulnerability in Unknown MStore API, published on 2 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The MStore API WordPress plugin before 4.22.1 does not restrict which fields of an order a customer may update, allowing any authenticated user with a self-registerable account to change the status of their own unpaid order to a paid or fulfilled state and receive the goods without paying.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-97219 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97219 is a medium-severity vulnerability in Unknown MStore API, published on 2 Oct 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-97219 in the wild and no public exploit code.

Affected product: Unknown MStore API. 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-97219/ (Markdown: https://insights.sbomify.com/CVE-2026-97219/index.md)
```

## Sources

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

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