MStore API – Create Native Android & iOS Apps On The Cloud <= 4.15.3 - Authenticated (Subscriber+) Limited Arbitrary File Upload
Strategic Overview
- Status
- Patched in 4.15.4
- Affected Plugin
- MStore API – Create Native Android & iOS Apps On The Cloud
- Affected Version
<= 4.15.3- CVSS
- 4.3Medium
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2024-8242
At a glance
CVE-2024-8242 is a medium-severity Unrestricted Upload of File with Dangerous Type vulnerability in the MStore API WordPress plugin, affecting versions <= 4.15.3. 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.15.4; sites on affected versions should update now. Disclosed September 2024, reported by stealthcopter.
Vulnerability Overview
The MStore API – Create Native Android & iOS Apps On The Cloud plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the update_user_profile() function in all versions up to, and including, 4.15.3. This makes it possible for authenticated attackers, with subscriber-level access and above, to upload arbitrary files (not including PHP files) on the affected site's server which may make remote code execution possible. This can be paired with a registration endpoint for unauthenticated users to exploit the issue.
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-434: Unrestricted Upload of File with Dangerous Type
MStore API <= 4.15.3 carries this weakness at update_user_profile(), and reaching it takes an account at Subscriber level or above. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.
If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For MStore API the fix is 4.15.4: builds <= 4.15.3 are affected, anything from 4.15.4 onward is not.
Remediation
Update to version 4.15.4, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: MStore API 4.15.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Same weakness class
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