MStore API 4.21.1 — 4.22.0 - Authenticated (Subscriber+) Payment Bypass
CVE-2026-97219Published · Updated Action summary
Affected: 4.21.1 – 4.22.0Update to 4.22.1 or newer
All remediation steps- Severity
- Medium4.3
- CVSS
- 4.3CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NWhat does this vector mean?
AV:NAttack vector- Network
AC:LAttack complexity- Low
PR:LPrivileges required- Low
UI:NUser interaction- None
S:UScope- Unchanged
C:NConfidentiality- None
I:LIntegrity- Low
A:NAvailability- None
- Required access
- Unknown
- Exploit prediction (EPSS)
- No score
- CISA KEV
- Not listed
On this page8
Am I affected?
MStore API – Create Native Android & iOS Apps On The Cloud mstore-api
- Affected4.21.1 – 4.22.0
- Patched in4.22.1
Update to 4.22.1 or newer.
You are affected if you run 4.21.1 – 4.22.0. Version 4.22.1 and later are not affected by this issue.
- Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under MStore API – Create Native Android & iOS Apps On The Cloud.
- No admin access? Run a passive check of your site. It reads public files only.
What to do
- Update to version 4.22.1, or a newer patched version
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
- Watch MStore API – Create Native Android & iOS Apps On The Cloud to get an email when the next vulnerability is published.
Advisory
Source description from Wordfence Intelligence, credited to cyberkareem.
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.
Exploits & references
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Related CVEs
More in MStore API – Create Native Android & iOS Apps On The Cloud
All 39| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Critical9.8 | Unauthenticated Authentication Bypass via 'id_token' Parameter JWT Forgery ≤4.20.0Update to 4.21.1 | CVE-2026-13447 | |
| Medium4.3 | Missing Authorization to Authenticated (Subscriber+) Arbitrary Order Completion <4.21.1Update to 4.21.1 | CVE-2026-18233 | |
| Medium6.3 | Missing Authorization <4.21.1Update to 4.21.1 | CVE-2026-18234 | |
| Critical9.8 | Unauthenticated Privilege Escalation ≤4.20.0Update to 4.21.0 | CVE-2026-27543 | |
| Medium5.3 | Missing Authorization ≤4.20.0Update to 4.21.0 | CVE-2026-16038 |
- Critical9.8Unauthenticated Authentication Bypass via 'id_token' Parameter JWT Forgery
≤4.20.0Update to 4.21.1
- Medium4.3Missing Authorization to Authenticated (Subscriber+) Arbitrary Order Completion
<4.21.1Update to 4.21.1
- Medium6.3Missing Authorization
<4.21.1Update to 4.21.1
- Critical9.8Unauthenticated Privilege Escalation
≤4.20.0Update to 4.21.0
- Medium5.3Missing Authorization
≤4.20.0Update to 4.21.0
Timeline
CVE published
Severity medium, CVSS 4.3
Record last updated
Sources & licenses
Wordfence record- Vulnerability data
- Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
- CVE® identifiers
- [object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
- CVSS / CWE
- National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.