CVE-2026-3568: CWE-639 Authorization Bypass Through User-Controlled Key in inspireui MStore API – Create Native Android & iOS Apps On The Cloud
CVE-2026-3568 is an authorization bypass vulnerability in the MStore API WordPress plugin up to version 4. 18. 3. It arises from the update_user_profile() function processing user-supplied meta_data JSON without validation, allowing authenticated users with Subscriber-level access or higher to modify arbitrary user meta fields on their own accounts. This includes sensitive fields such as wp_user_level, which can be used to escalate privileges, and plugin-specific authorization flags. The vulnerability does not allow direct exploitation of wp_capabilities but does permit modification of simpler meta keys. The CVSS score is 4. 3, indicating medium severity. No official patch or remediation guidance is currently available from the vendor.
AI Analysis
Technical Summary
The MStore API plugin for WordPress contains an Insecure Direct Object Reference vulnerability (CWE-639) in the update_user_profile() function within controllers/flutter-user.php. This function reads raw JSON input from php://input, decodes it, authenticates the user via cookie validation, and then iterates over the user-supplied meta_data array without any allowlist, blocklist, or validation of meta keys. Consequently, authenticated users with Subscriber-level privileges or above can update arbitrary user meta fields on their own accounts, including sensitive fields like wp_user_level (which can be used for privilege escalation) and plugin-specific authorization flags. The vulnerability does not permit direct modification of wp_capabilities due to its serialized array format requirement but does allow modification of other critical meta keys. The issue affects all versions up to and including 4.18.3. No patch or official remediation has been published yet.
Potential Impact
An authenticated attacker with Subscriber-level access or higher can modify arbitrary user meta fields on their own account, including sensitive fields that can lead to privilege escalation (e.g., wp_user_level) and manipulation of plugin-specific authorization flags. This could allow an attacker to gain administrator-level privileges or alter billing/profile information with unsanitized input, potentially enabling stored cross-site scripting (XSS) in administrative contexts. The vulnerability does not impact confidentiality or availability directly but poses an integrity risk through unauthorized modification of user metadata.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, restrict user roles and permissions carefully and monitor for suspicious activity related to user meta modifications. Avoid granting Subscriber-level or higher access to untrusted users. Consider implementing custom validation or sanitization for user meta updates if possible.
CVE-2026-3568: CWE-639 Authorization Bypass Through User-Controlled Key in inspireui MStore API – Create Native Android & iOS Apps On The Cloud
Description
CVE-2026-3568 is an authorization bypass vulnerability in the MStore API WordPress plugin up to version 4. 18. 3. It arises from the update_user_profile() function processing user-supplied meta_data JSON without validation, allowing authenticated users with Subscriber-level access or higher to modify arbitrary user meta fields on their own accounts. This includes sensitive fields such as wp_user_level, which can be used to escalate privileges, and plugin-specific authorization flags. The vulnerability does not allow direct exploitation of wp_capabilities but does permit modification of simpler meta keys. The CVSS score is 4. 3, indicating medium severity. No official patch or remediation guidance is currently available from the vendor.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The MStore API plugin for WordPress contains an Insecure Direct Object Reference vulnerability (CWE-639) in the update_user_profile() function within controllers/flutter-user.php. This function reads raw JSON input from php://input, decodes it, authenticates the user via cookie validation, and then iterates over the user-supplied meta_data array without any allowlist, blocklist, or validation of meta keys. Consequently, authenticated users with Subscriber-level privileges or above can update arbitrary user meta fields on their own accounts, including sensitive fields like wp_user_level (which can be used for privilege escalation) and plugin-specific authorization flags. The vulnerability does not permit direct modification of wp_capabilities due to its serialized array format requirement but does allow modification of other critical meta keys. The issue affects all versions up to and including 4.18.3. No patch or official remediation has been published yet.
Potential Impact
An authenticated attacker with Subscriber-level access or higher can modify arbitrary user meta fields on their own account, including sensitive fields that can lead to privilege escalation (e.g., wp_user_level) and manipulation of plugin-specific authorization flags. This could allow an attacker to gain administrator-level privileges or alter billing/profile information with unsanitized input, potentially enabling stored cross-site scripting (XSS) in administrative contexts. The vulnerability does not impact confidentiality or availability directly but poses an integrity risk through unauthorized modification of user metadata.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, restrict user roles and permissions carefully and monitor for suspicious activity related to user meta modifications. Avoid granting Subscriber-level or higher access to untrusted users. Consider implementing custom validation or sanitization for user meta updates if possible.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-03-04T20:45:42.536Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69d71b0f1cc7ad14da048cc6
Added to database: 4/9/2026, 3:20:47 AM
Last enriched: 4/16/2026, 12:24:02 PM
Last updated: 5/25/2026, 12:23:26 PM
Views: 55
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.