CVE-2024-6328

MStore API – Create Native Android & iOS Apps On The Cloud <= 4.14.7 - Authentication Bypass

2024-07-11 00:00
Truoc Phan

Strategic Overview

Status
Patched in 4.15.0
Affected Plugin
MStore API – Create Native Android & iOS Apps On The Cloud
Affected Version
<= 4.14.7
CVSS
9.8Critical
Weakness type
CWE-288 · Authentication Bypass Using an Alternate Path or Channel
CVE
CVE-2024-6328
View all MStore API – Create Native Android & iOS Apps On The Cloud vulnerabilities

At a glance

CVE-2024-6328 is a critical-severity Authentication Bypass Using an Alternate Path or Channel vulnerability in the MStore API WordPress plugin, affecting versions <= 4.14.7. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 4.15.0; sites on affected versions should update now. Disclosed July 2024, reported by Truoc Phan.

Vulnerability Overview

The MStore API – Create Native Android & iOS Apps On The Cloud plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 4.14.7. This is due to insufficient verification on the 'phone' parameter of the 'firebase_sms_login' and 'firebase_sms_login_v2' functions. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if they have access to the email address or phone number. Additionally, if a new email address is supplied, a new user account is created with the default role, even if registration is disabled.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-288: Authentication Bypass Using an Alternate Path or Channel

MStore API <= 4.14.7 carries this weakness at phone, and reaching it takes a caller who can reach the endpoint. Authentication bypass through an alternate path means the application has a second route to a protected action that skips the checks the primary route performs.

The protection on the main path becomes irrelevant, because the attacker simply uses the route that never asks. For MStore API the fix is 4.15.0: builds <= 4.14.7 are affected, anything from 4.15.0 onward is not.

Remediation

Update to version 4.15.0, 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.0 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-6328https://www.wordfence.com/threat-intel/vulnerabilities/id/17d8e2e9-5e3f-433b-be1a-6ea765eba547https://nvd.nist.gov/vuln/detail/CVE-2024-6328

Related records

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