WordPress plugin · mstore-api
Is MStore API safe?
Safe on 4.22.1 or newer.
The current version, 4.22.1, is past every affected range on record (40 of 41 records list one; 1 doesn’t, so check it below). Keep it updated and you’re clear of them.
- Flaws on record
- 41
- High or critical
- 20
- Exploited
- none
- Current version
- 4.22.1
- Last updated
- Sep 29, 2026
- Active installs
- 2,000+
Every recorded flaw
- Oct 2, 2026MStore API: Does not restrictCVE-2026-97219 · fixed in 4.22.1 · reported by WPScanMedium 4.3
- Sep 5, 2026Mstore Api: Authentication BypassCVE-2026-13447 · affects up to 4.20.0 · reported by WordfenceCritical 9.8
- Aug 29, 2026MStore API: Does not verify that the order targeted by its wallet payment handling belongs to the requesterCVE-2026-18234 · fixed in 4.21.1 · reported by WPScanMedium 6.5
- Aug 29, 2026MStore API: Does not verify that the order targeted by one of its delivery endpoints belongs to the requesterCVE-2026-18233 · fixed in 4.21.1 · reported by WPScanMedium 6.5
- Aug 13, 2026Unauthenticated Privilege Escalation in MStore API <= 4.20.0 versions.CVE-2026-27543 · affects up to 4.20.0 · reported by PatchstackHigh 8.1
- Aug 7, 2026MStore API: Does not perform authorization or purchase-ownership checks on its REST product-review creation routeCVE-2026-16041 · fixed in 4.21.0 · reported by WPScanHigh 7.5
- Aug 7, 2026MStore API: Does not restrict its vendor-orders endpoint to the caller's own ordersCVE-2026-16039 · fixed in 4.21.0 · reported by WPScanMedium 6.5
- Aug 7, 2026MStore API: Does not verify the payment with the payment gateway before marking an orderCVE-2026-16038 · fixed in 4.21.0 · reported by WPScanCritical 9.1
- Aug 7, 2026MStore API: Does not correctly verify the cryptographic signature of the token used to authenticate its phone-based loginCVE-2026-16030 · fixed in 4.21.0 · reported by WPScanHigh 8.1
- Jul 13, 2026MStore API: Missing AuthorizationCVE-2026-57375 · affects up to 4.18.4 · reported by PatchstackMedium 6.5
- Jun 17, 2026MStore API: Authentication Bypass Using an Alternate Path or ChannelCVE-2026-54817 · affects up to 4.18.4 · reported by PatchstackMedium 6.5
- May 10, 2026WordPress MStore API 2.0.6 contains an arbitrary file upload vulnerability that allows unauthenticated attackers to upload malicious files by sending POST requeCVE-2021-47933 · reported by VulnCheckCritical 9.3
- Apr 9, 2026MStore API: Insecure Direct Object ReferenceCVE-2026-3568 · affects up to 4.18.3 · reported by WordfenceMedium 4.3
- May 26, 2025MStore API – Create Native Android & iOS Apps On The Cloud: Unauthorized modification of dataCVE-2025-4683 · affects up to 4.17.5 · reported by WordfenceMedium 4.3
- May 2, 2025MStore API – Create Native Android & iOS Apps On The Cloud: Limited privilege escalationCVE-2025-3438 · affects up to 4.17.4 · reported by WordfenceMedium 6.5
- Dec 13, 2024MStore API – Create Native Android & iOS Apps On The Cloud: Stored Cross-Site ScriptingCVE-2024-12042 · affects up to 4.16.4 · reported by WordfenceMedium 5.4
- Nov 20, 2024MStore API – Create Native Android & iOS Apps On The Cloud: SQL InjectionCVE-2024-11179 · affects up to 4.15.7 · reported by WordfenceMedium 6.5
- Sep 13, 2024MStore API – Create Native Android & iOS Apps On The Cloud: Unauthorized user registrationCVE-2024-8269 · affects up to 4.15.3 · reported by WordfenceHigh 7.3
- Sep 13, 2024MStore API – Create Native Android & iOS Apps On The Cloud: Arbitrary file uploadsCVE-2024-8242 · affects up to 4.15.3 · reported by WordfenceMedium 4.3
- Aug 14, 2024MStore API – Create Native Android & iOS Apps On The Cloud: Authentication bypassCVE-2024-7628 · affects up to 4.15.2 · reported by WordfenceHigh 8.1
- Jul 12, 2024MStore API – Create Native Android & iOS Apps On The Cloud: Authentication bypassCVE-2024-6328 · affects up to 4.14.7 · reported by WordfenceCritical 9.8
- Dec 29, 2023MStore API: Cross-Site Request Forgery (CSRF)CVE-2023-50878 · affects up to 4.10.1 · reported by PatchstackMedium 5.4
- Nov 6, 2023MStore API: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')CVE-2023-45055 · affects up to 4.0.6 · reported by PatchstackHigh 8.5
- Nov 3, 2023MStore API: Unauthorized Account Access and Privilege EscalationCVE-2023-3277 · affects up to 4.10.7 · reported by Wordfence2.9% oddsCritical 9.8
- Jul 12, 2023MStore API: Cross-Site Request ForgeryCVE-2023-3202 · affects up to 3.9.6 · reported by WordfenceMedium 4.3
- Jul 12, 2023MStore API: Cross-Site Request ForgeryCVE-2023-3199 · affects up to 3.9.6 · reported by WordfenceMedium 4.3
- Jul 10, 2023MStore API: Does not secure most of its AJAX actions by implementing privilege checksCVE-2023-3209 · fixed in 3.9.7 · reported by WPScanLow 3.5
- Jul 10, 2023MStore API: Does not secure most of its AJAX actions by implementing privilege checksCVE-2023-3131 · fixed in 3.9.7 · reported by WPScanMedium 4.3
- Jul 10, 2023MStore API: Does not sanitise and escape a parameter before using it in a SQL statementCVE-2023-3077 · fixed in 3.9.8 · reported by WPScan5.5% oddsCritical 9.8
- Jul 10, 2023MStore API: Does not prevent visitors from creating user accounts with the role of their choice via their wholesale REST API endpointCVE-2023-3076 · fixed in 3.9.9 · reported by WPScan2.2% oddsCritical 9.8
- Jun 23, 2023MStore API: Unauthenticated Blind SQL InjectionCVE-2023-3197 · affects up to 4.0.1 · reported by Wordfence3.9% oddsCritical 9.8
- Jun 23, 2023Unauth.CVE-2022-47614 · affects up to 3.9.7 · reported by PatchstackHigh 7.5
- Jun 13, 2023MStore API: Cross-Site Request ForgeryCVE-2023-3203 · affects up to 3.9.6 · reported by WordfenceMedium 4.3
- Jun 13, 2023MStore API: Cross-Site Request ForgeryCVE-2023-3201 · affects up to 3.9.6 · reported by WordfenceMedium 4.3
- Jun 13, 2023MStore API: Cross-Site Request ForgeryCVE-2023-3200 · affects up to 3.9.6 · reported by WordfenceMedium 4.3
- Jun 13, 2023MStore API: Cross-Site Request ForgeryCVE-2023-3198 · affects up to 3.9.6 · reported by WordfenceMedium 4.3
- Jun 6, 2023MStore API: Authentication bypassCVE-2020-36713 · affects up to 2.1.5 · reported by Wordfence1.6% oddsCritical 9.8
- May 24, 2023MStore API: Authentication bypassCVE-2023-2734 · affects up to 3.9.1 · reported by Wordfence3.8% oddsCritical 9.8
- May 24, 2023MStore API: Authentication bypassCVE-2023-2733 · affects up to 3.9.0 · reported by Wordfence1.2% oddsCritical 9.8
- May 24, 2023MStore API: Authentication bypassCVE-2023-2732 · affects up to 3.9.2 · reported by Wordfence67% oddsCritical 9.8
- Mar 18, 2021A business logic issue in the MStore API WordPress plugin, versions before 3.2.0, had an authentication bypass with Sign In With Apple allowing unauthenticated CVE-2021-24148 · fixed in 3.2.0 · reported by WPScan3.4% oddsCritical 9.8
Records come from the National Vulnerability Database, published by the researchers who found each flaw (Wordfence, Patchstack, WPScan and others); exploited status from CISA; exploit odds from FIRST’s EPSS; current version, installs and closures from wordpress.org, checked daily. Want every plugin on your site checked at once? Run the free website check.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Get in touch
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
01The person who'll do the work writes back
02A short call, then a written plan with the price
03Nothing starts until you say yes
04Hacked or down right now? Call, and we pick up the same day
Not ready to talk yet? Run the free website check and see what Google sees.