CVE-2026-3568 MEDIUM

CVE-2026-3568: MStore API <= 4.18.3 - Authenticated (Subscriber+) Insecure Direct Object Reference to Arbitrary User Meta Update

Vendor Inspireui
Product MStore API – Create Native Android & iOS Apps On The Cloud
Weakness CWE-639 · IDOR
Published April 9, 2026
Last update April 9, 2026

CVSS base score

4.3/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

MStore API versions up to 4.18.3 contain an authorization flaw that allows authenticated users to modify data they should not have access to. The vulnerability requires a valid user account and network access but no additional user interaction. Site owners using this product should update to a patched version to prevent unauthorized data modification.

What an attacker can do

03Attacker Capabilities

Modify data or settings they are not authorized to change.

Potential impact on your site

04Site Impact

Authenticated users can alter application data or configuration outside their intended permissions.

Conditions required to exploit

05Prerequisites

Attacker must have a valid user account on the site.

Key dates

06Disclosure timeline

April 9, 2026 CVE published
April 9, 2026 Record updated

Related vulnerabilities

08Related CVE