Skip to main content
CVE-2024-6328VulnerabilityPublished Updated

CVE-2024-6328: MStore API (WordPress plugin) · Authentication Bypass Using an Alternate Path or Channel

Affects MStore API (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · patch available : patch MStore API (WordPress plugin) as a priority.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Jul 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
inspireui MStore API – Create Native Android & iOS Apps On The CloudAffected
  • =0
Fixed in–

AI-suggested

A patch is available for this vulnerability. Users of the MStore API plugin should apply the official update to version 4.14.8 or later as soon as possible to remediate the authentication bypass issue. Until patched, restricting access to the plugin's login endpoints and monitoring for suspicious activity may help reduce risk, but patching is the definitive mitigation.

Description

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.

References

Community reviews

Loading reviews…