CVE-2024-6328
Inspireui Mstore API authentication bypass
- Published12 Jul 2024
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://plugins.trac.wordpress.org/browser/mstore-api/trunk/controllers/flutter-user.php#L699
- https://plugins.trac.wordpress.org/browser/mstore-api/trunk/controllers/flutter-user.php#L714
- https://plugins.trac.wordpress.org/changeset/3115231/
- https://www.wordfence.com/threat-intel/vulnerabilities/id/17d8e2e9-5e3f-433b-be1a-6ea765eba547?source=cve
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2024-6328 being actively exploited?
CVE-2024-6328 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.67%.
How severe is CVE-2024-6328?
CVE-2024-6328 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.67% probability of exploitation.
Which products are affected by CVE-2024-6328?
Affected products include Inspireui Mstore API.
How do I fix CVE-2024-6328?
Upgrade affected software to a fixed version, for example Inspireui Mstore API 4.15.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2024-6328 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.