Radar sectionsDatabase
Check my site
WordPress plugin

MStore API <= 4.18.3 — Authenticated (Subscriber+) Insecure Direct Object Reference to Arbitrary User Meta Update

CVE-2026-3568Published · Updated

Action summary

Affected: ≤4.18.3Update to 4.18.4 or newer

All remediation steps
Severity
Medium4.3
CVSS
4.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:L Privileges required
Low
UI:N User interaction
None
S:U Scope
Unchanged
C:N Confidentiality
None
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-639 Authorization Bypass Through User-Controlled Key
Required access
Unknown
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

MStore API – Create Native Android & iOS Apps On The Cloud mstore-api

  1. Affected≤ 4.18.3
  2. Patched in4.18.4

Update to 4.18.4 or newer.

You are affected if you run ≤ 4.18.3. Version 4.18.4 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under MStore API – Create Native Android & iOS Apps On The Cloud.
  • No admin access? Run a passive check of your site. It reads public files only.

What to do

  1. Update to version 4.18.4, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch MStore API – Create Native Android & iOS Apps On The Cloud to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Osvaldo Noe Gonzalez Del Rio (Os).

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in MStore API – Create Native Android & iOS Apps On The Cloud

All 39
More vulnerabilities in MStore API – Create Native Android & iOS Apps On The Cloud
SeverityVulnerabilityCVEPublished
Medium4.34.22.0 - Authenticated (Subscriber+) Payment Bypass
4.21.1 – 4.22.0Update to 4.22.1
CVE-2026-97219
Critical9.8Unauthenticated Authentication Bypass via 'id_token' Parameter JWT Forgery
≤4.20.0Update to 4.21.1
CVE-2026-13447
Medium4.3Missing Authorization to Authenticated (Subscriber+) Arbitrary Order Completion
<4.21.1Update to 4.21.1
CVE-2026-18233
Medium6.3Missing Authorization
<4.21.1Update to 4.21.1
CVE-2026-18234
Critical9.8Unauthenticated Privilege Escalation
≤4.20.0Update to 4.21.0
CVE-2026-27543

Timeline

  1. CVE published

    Severity medium, CVSS 4.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?