CVE-2024-7628

MStore API – Create Native Android & iOS Apps On The Cloud <= 4.15.2 - Authentication Bypass to Account Takeover

2024-08-14 14:08
Truoc Phan

Strategic Overview

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

At a glance

CVE-2024-7628 is a high-severity Authentication Bypass Using an Alternate Path or Channel vulnerability in the MStore API WordPress plugin, affecting versions <= 4.15.2. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 4.15.3; sites on affected versions should update now. Disclosed August 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 versions up to, and including, 4.15.2. This is due to the use of loose comparison in the 'verify_id_token' function. 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 an @flutter.io email address or phone number. This also requires firebase to be configured on the website and the user to have set up firebase for their account.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, 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.15.2 carries this weakness at verify_id_token, 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.3: builds <= 4.15.2 are affected, anything from 4.15.3 onward is not.

Remediation

Update to version 4.15.3, 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.3 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-7628https://www.wordfence.com/threat-intel/vulnerabilities/id/d174f856-d94a-42ed-b547-67699e175cd8https://nvd.nist.gov/vuln/detail/CVE-2024-7628

Related records

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