CVE-2024-8269 json
MStore API – Create Native Android & iOS Apps On The Cloud <= 4.15.3 - Unauthorized User Registration
published 2024-09-13 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-49056
- cvss
- 7.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- inspireui mstore_api 4.15.4
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
Affected products
- inspireui MStore API – Create Native Android & iOS Apps On The Cloud
- fluxbuilder mstore_api
Classification
- Weakness
-
- CWE-284 Improper Access Control
- Technology feeds
References
-
plugins.trac.wordpress.org
/changeset/3147900/mstore-api/trunk/controllers/flutter-user.php
patch
-
wordfence.com
/threat-intel/vulnerabilities/id/59c5b6e7-74b0-430d-8b4a-5a42220f3ec9?source=cve
third-party-advisory
-
plugins.trac.wordpress.org
/browser/mstore-api/tags/4.15.2/controllers/flutter-user.php#L406
product
-
plugins.trac.wordpress.org
/browser/mstore-api/tags/4.15.2/controllers/flutter-user.php#L454
product
Sources
- CVE List CVE-2024-8269
- NVD CVE-2024-8269
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.