MStore API – Create Native Android & iOS Apps On The Cloud <= 4.17.4 - Unauthenticated Limited Privilege Escalation
Strategic Overview
- Status
- Patched in 4.17.5
- Affected Plugin
- MStore API – Create Native Android & iOS Apps On The Cloud
- Affected Version
<= 4.17.4- CVSS
- 6.5Medium
- Weakness type
- CWE-269 · Improper Privilege Management
- CVE
CVE-2025-3438
At a glance
CVE-2025-3438 is a medium-severity Improper Privilege Management vulnerability in the MStore API WordPress plugin, affecting versions <= 4.17.4. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.17.5; sites on affected versions should update now. Disclosed May 2025, reported by Brian Sans-Souci (liardom).
Vulnerability Overview
The MStore API – Create Native Android & iOS Apps On The Cloud plugin for WordPress is vulnerable to limited privilege escalation in all versions up to, and including, 4.17.4. This is due to a lack of restriction of role when registering. This makes it possible for unauthenticated attackers to to register with the 'wcfm_vendor' role, which is a Store Vendor role in the WCFM Marketplace – Multivendor Marketplace for WooCommerce plugin for WordPress. The vulnerability can only be exploited if the WCFM Marketplace – Multivendor Marketplace for WooCommerce plugin is installed and activated. The vulnerability was partially patched in version 4.17.3.
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 privileges on the target site, and no interaction from a victim user.
CWE-269: Improper Privilege Management
MStore API <= 4.17.4 carries this weakness at wcfm_vendor, and reaching it takes no account at all. Improper privilege management means the code lets an account end up with capabilities its role should not have.
It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For MStore API the fix is 4.17.5: builds <= 4.17.4 are affected, anything from 4.17.5 onward is not.
Remediation
Update to version 4.17.5, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: MStore API 4.17.5 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in MStore API – Create Native Android & iOS Apps On The Cloud
- 9.8CVE-2026-13447: MStore API <= 4.20.0 Authentication Bypass
CVE-2026-13447 - 9.8CVE-2026-27543: MStore API Privilege Escalation
CVE-2026-27543 - 9.8CVE-2024-6328: MStore API Authentication Bypass
CVE-2024-6328 - 9.8CVE-2023-3197: MStore API <= 4.0.1 SQL Injection
CVE-2023-3197 - 9.8CVE-2023-3277: MStore API Unauthorized Account Access and Privilege
CVE-2023-3277 - 9.8CVE-2022-47614: MStore API <= 3.9.7 SQL Injection
CVE-2022-47614 - 9.8CVE-2023-3076: MStore API <= 3.9.8 Privilege Escalation
CVE-2023-3076 - 9.8CVE-2023-3077: MStore API <= 3.9.7 SQL Injection
CVE-2023-3077
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C