CVE-2026-97219

MStore API 4.21.1 - 4.22.0 - Authenticated (Subscriber+) Payment Bypass

2026-09-30 00:00
cyberkareem

Strategic Overview

Status
Patched in 4.22.1
Affected Version
4.21.1 – 4.22.0
CVSS
4.3Medium
Weakness type
CWE-602 · Client-Side Enforcement of Server-Side Security
CVE
CVE-2026-97219
View all MStore API – Create Native Android & iOS Apps On The Cloud vulnerabilities

At a glance

CVE-2026-97219 is a medium-severity Client-Side Enforcement of Server-Side Security vulnerability in the MStore API WordPress plugin, affecting versions 4.21.1 – 4.22.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.22.1; sites on affected versions should update now. Disclosed September 2026, reported by cyberkareem.

Vulnerability Overview

The MStore API plugin for WordPress is vulnerable to Payment Bypass in versions 4.21.1 through 4.22.0. This is due to a lack of server-side payment verification. This makes it possible for authenticated attackers, with subscriber-level access and above, to bypass payments.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-602: Client-Side Enforcement of Server-Side Security

The product is composed of a server that relies on the client to implement a mechanism that is intended to protect the server.

Remediation

Update to version 4.22.1, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: MStore API 4.22.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C