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

> Authenticated attackers can modify arbitrary user meta fields, potentially escalating privileges or injecting malicious data due to lack of validation.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Apr 2026
- **Updated:** 9 Apr 2026
- **Also known as:** GHSA-fg73-jmcf-5xr8

## What is CVE-2026-3568?

CVE-2026-3568 is a medium-severity missing authorization vulnerability in inspireui MStore API – Create Native Android & iOS Apps On The Cloud, published on 9 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-3568?


## How do I fix CVE-2026-3568?

No fix has been published for CVE-2026-3568 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-3568 being exploited?

There is no known exploitation of CVE-2026-3568 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-3568 and fix it if it is affected.

What it is: CVE-2026-3568 is a medium-severity missing authorization vulnerability in inspireui MStore API – Create Native Android & iOS Apps On The Cloud, published on 9 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-3568 in the wild and no public exploit code.

Affected product: inspireui MStore API – Create Native Android & iOS Apps On The Cloud. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-3568/ (Markdown: https://insights.sbomify.com/CVE-2026-3568/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-3568
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3568
- OSV: https://osv.dev/vulnerability/CVE-2026-3568

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-3568/
Summaries are generated and may contain mistakes; the official description above is the record.