Medium severity · published Oct 2, 2026
CVE-2026-97219
MStore API 4.21.1 - 4.22.0 - Subscriber+ Payment Bypass via 'status' Parameter
4.3
CVSS
0.2%
EPSS
No
On KEV
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.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Confidentiality
None
Integrity
Low
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.2% · higher than 8% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
MA
MStore API ·
4.21.1 before 4.22.1 · source: vendor
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-97219
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-97219
exploit
https://wpscan.com/vulnerability/0787d00b-2263-465f-8f46-906741bf6629/
More from MStore API
9.8
CVE-2023-3077
MStore API < 3.9.8 - Unauthenticated Blind SQLi
9.8
CVE-2023-3076
MStore API < 3.9.9 - Unauthenticated Privilege Escalation
9.1
CVE-2026-16038
MStore API < 4.21.0 - Unauthenticated Payment Bypass via Multiple Payment Gateways
8.1
CVE-2026-16030
MStore API < 4.21.0 - Unauthenticated Account Takeover via Firebase Phone Authentication
7.5
CVE-2026-16041
MStore API < 4.21.0 - Unauthenticated Product Review Creation