PatchTheCVEmstore api vulnerabilities and fixes
Recent CVEs affecting mstore api, with upgrade or downgrade steps. 6 tracked.
Also searched as: mstoreapi.
mstore api has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 6. Most recent: 2025-05-27. Highest priority: CVE-2024-8269 (score 39/100).
- CVE-2025-4683 MEDIUM 4.3 UPGRADE The MStore API – Create Native Android & iOS Apps On The Cloud plugin for WordPress is vulnerable to unauthori
- CVE-2025-3438 MEDIUM 6.5 UPGRADE The MStore API – Create Native Android & iOS Apps On The Cloud plugin for WordPress is vulnerable to limited p
- CVE-2024-8269 HIGH 7.3 UPGRADE The MStore API – Create Native Android & iOS Apps On The Cloud plugin for WordPress is vulnerable to unauthori
- CVE-2024-8242 MEDIUM 4.3 UPGRADE The MStore API – Create Native Android & iOS Apps On The Cloud plugin for WordPress is vulnerable to arbitrary
- CVE-2024-12042 MEDIUM 5.4 UPGRADE The MStore API – Create Native Android & iOS Apps On The Cloud plugin for WordPress is vulnerable to Stored Cr
- CVE-2024-11179 MEDIUM 6.5 UPGRADE The MStore API – Create Native Android & iOS Apps On The Cloud plugin for WordPress is vulnerable to SQL Injec
FAQ
How do I fix mstore api vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is mstore api being exploited right now?
None of the tracked mstore api CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which mstore api CVE should I patch first?
CVE-2024-8269 currently ranks highest (39/100): The MStore API – Create Native Android & iOS Apps On The Cloud plugin for WordPress is vulnerable to unauthori.