CVE-2024-8269

MStore API – Create Native Android & iOS Apps On The Cloud <= 4.15.3 - Unauthorized User Registration

2024-09-12 00:00
wesley (wcraft)

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
7.3High
Weakness type
CWE-284 · Improper Access Control
CVE
CVE-2024-8269
View all MStore API – Create Native Android & iOS Apps On The Cloud vulnerabilities

At a glance

CVE-2024-8269 is a high-severity Improper Access Control vulnerability in the MStore API WordPress plugin, affecting versions <= 4.15.3. It carries a CVSS score of 7.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.15.4; sites on affected versions should update now. Disclosed September 2024, reported by wesley (wcraft).

Vulnerability Overview

The MStore API – Create Native Android & iOS Apps On The Cloud plugin for WordPress is vulnerable to unauthorized user registration in all versions up to, and including, 4.15.3. This is due to the plugin not checking that user registration is enabled prior to creating a user account through the register() function. This makes it possible for unauthenticated attackers to create user accounts on sites, even when user registration is disabled and plugin functionality is not activated.

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-284: Improper Access Control

MStore API <= 4.15.3 carries this weakness at register(), and reaching it takes a caller who can reach the endpoint. Improper access control means the code decides what a caller may do using something other than their actual permissions, so the decision can be wrong without any check appearing to be missing.

Whoever can shape the request decides the answer, so the protected action runs for callers the code never meant to allow. 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?

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.15.4 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-8269https://www.wordfence.com/threat-intel/vulnerabilities/id/59c5b6e7-74b0-430d-8b4a-5a42220f3ec9https://nvd.nist.gov/vuln/detail/CVE-2024-8269

Related records

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