Inspireui Inspireui

Don't miss out!

Thousands of developers use stack.watch to stay informed.
Get an email whenever new security vulnerabilities are reported in any Inspireui product.

RSS Feeds for Inspireui security vulnerabilities

Create a CVE RSS feed including security vulnerabilities found in Inspireui products with stack.watch. Just hit watch, then grab your custom RSS feed url.

Products by Inspireui Sorted by Most Security Vulnerabilities since 2018

Inspireui Mstore Api29 vulnerabilities

By the Year

In 2026 there have been 1 vulnerability in Inspireui with an average score of 4.3 out of ten. Last year, in 2025 Inspireui had 2 security vulnerabilities published. If vulnerabilities keep coming in at the current rate, it appears that number of security vulnerabilities in Inspireui in 2026 could surpass last years number. Last year, the average CVE base score was greater by 1.50




Year Vulnerabilities Average Score
2026 1 4.30
2025 2 5.80
2024 6 6.77
2023 19 7.27
2022 0 0.00
2021 1 9.80

It may take a day or so for new Inspireui vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.

Recent Inspireui Security Vulnerabilities

CVE Date Vulnerability Products
CVE-2026-3568 Apr 09, 2026
CVE-2026-3568: IDOR in MStore API Plugin WordPress <=4.18.3 The MStore API plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.18.3. This is due to the update_user_profile() function in controllers/flutter-user.php processing the 'meta_data' JSON parameter without any allowlist, blocklist, or validation of meta keys. The function reads raw JSON from php://input (line 1012), decodes it (line 1013), authenticates the user via cookie validation (line 1015), and then directly iterates over the user-supplied meta_data array passing arbitrary keys and values to update_user_meta() (line 1080) with no sanitization or restrictions. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify arbitrary user meta fields on their own accounts, including sensitive fields like wp_user_level (to escalate to administrator-level legacy checks), plugin-specific authorization flags (e.g., _wpuf_user_active, aiowps_account_status), and billing/profile fields with unsanitized values (potentially enabling Stored XSS in admin contexts). Note that wp_capabilities cannot be directly exploited this way because it requires a serialized array value, but wp_user_level (a simple integer) and numerous plugin-specific meta keys are exploitable.
Mstore Api
CVE-2025-4683 May 27, 2025
Unauthorized Data Mod in MStore API Cmd Native Android/iOS Apps Plugin <=4.17.5 The MStore API Create Native Android & iOS Apps On The Cloud plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the create_blog function in all versions up to, and including, 4.17.5. This makes it possible for authenticated attackers, with Subscriber-level access and above, to create new posts.
Mstore Api
CVE-2025-3438 May 02, 2025
MStore API Plugin 4.17.4 – Unauth Priv Esc via role bypass (WordPress) The MStore API Create Native Android & iOS Apps On The Cloud plugin for WordPress is vulnerable to limited privilege escalation in all versions up to, and including, 4.17.4. This is due to a lack of restriction of role when registering. This makes it possible for unauthenticated attackers to to register with the 'wcfm_vendor' role, which is a Store Vendor role in the WCFM Marketplace Multivendor Marketplace for WooCommerce plugin for WordPress. The vulnerability can only be exploited if the WCFM Marketplace Multivendor Marketplace for WooCommerce plugin is installed and activated. The vulnerability was partially patched in version 4.17.3.
Mstore Api
CVE-2024-12042 Dec 13, 2024
MStore API Plugin for WordPress: Stored XSS via Profile Picture Upload The MStore API Create Native Android & iOS Apps On The Cloud plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the profile picture upload functionality in all versions up to, and including, 4.16.4 due to insufficient file type validation. This makes it possible for authenticated attackers, with subscriber-level access and above, to upload HTML files with arbitrary web scripts that will execute whenever a user accesses the file.
Mstore Api
CVE-2024-11179 Nov 20, 2024
SQL Injection Vulnerability in MStore API Plugin for WordPress The MStore API Create Native Android & iOS Apps On The Cloud plugin for WordPress is vulnerable to SQL Injection via the 'status_type' parameter in all versions up to, and including, 4.15.7 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Mstore Api
CVE-2024-8269 Sep 13, 2024
Unauthorized User Registration in MStore API Plugin v<=4.15.3 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.
Mstore Api
CVE-2024-8242 Sep 13, 2024
MStore API WP Plugin 4.15.3 File Upload Vulnerability The MStore API Create Native Android & iOS Apps On The Cloud plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the update_user_profile() function in all versions up to, and including, 4.15.3. This makes it possible for authenticated attackers, with subscriber-level access and above, to upload arbitrary files (not including PHP files) on the affected site's server which may make remote code execution possible. This can be paired with a registration endpoint for unauthenticated users to exploit the issue.
Mstore Api
CVE-2024-7628 Aug 15, 2024
Auth Bypass in MStore API WP Plugin 4.15.2 via verify_id_token Loose Comparison 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.
Mstore Api
Mstore Api Create Native Android Ios Apps On Cloud
CVE-2024-6328 Jul 12, 2024
MStore API WP Plugin Auth Bypass via Firebase SMS Login up to v4.14.7 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.
Mstore Api
CVE-2023-50878 Dec 29, 2023
InspireUI MStore API CSRF in <4.10.1 Cross-Site Request Forgery (CSRF) vulnerability in InspireUI MStore API.This issue affects MStore API: from n/a through 4.10.1.
Mstore Api
Built by Foundeo Inc., with data from the National Vulnerability Database (NVD). Privacy Policy. Use of this site is governed by the Legal Terms
Disclaimer
CONTENT ON THIS WEBSITE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR USE. YOUR USE OF THE INFORMATION ON THE DOCUMENT OR MATERIALS LINKED FROM THE DOCUMENT IS AT YOUR OWN RISK. Always check with your vendor for the most up to date, and accurate information.