{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-3568 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-3568 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-3568 is a medium-severity missing authorization vulnerability in inspireui MStore API – Create Native Android \u0026 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."},"fix_prompt":"Check this codebase for CVE-2026-3568 and fix it if it is affected.\n\nWhat it is: CVE-2026-3568 is a medium-severity missing authorization vulnerability in inspireui MStore API – Create Native Android \u0026 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.\nExploitation: There is no known exploitation of CVE-2026-3568 in the wild and no public exploit code.\n\nAffected product: inspireui MStore API – Create Native Android \u0026 iOS Apps On The Cloud. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-3568/ (Markdown: https://insights.sbomify.com/CVE-2026-3568/index.md)","id":"CVE-2026-3568","markdown":"https://insights.sbomify.com/CVE-2026-3568/index.md","name":"CVE-2026-3568","record":{"aliases":["GHSA-fg73-jmcf-5xr8"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated attackers can modify arbitrary user meta fields, potentially escalating privileges or injecting malicious data due to lack of validation.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"MStore API \u003c= 4.18.3 - Authenticated (Subscriber+) Insecure Direct Object Reference to Arbitrary User Meta Update","id":"CVE-2026-3568","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"Missing authorization in Liaison Site Prober","id":"CVE-2026-3569"},"packages":[],"prev":{"headline":"Missing authorization in RepairBuddy – Repair Shop CRM \u0026 Booking Plugin for WordPress","id":"CVE-2026-3567"},"products":["MStore API – Create Native Android \u0026 iOS Apps On The Cloud"],"published":"2026-04-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-09","vendors":["inspireui"]},"summary":"Authenticated attackers can modify arbitrary user meta fields, potentially escalating privileges or injecting malicious data due to lack of validation.","url":"https://insights.sbomify.com/CVE-2026-3568/"}