{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-3201 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-3201 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-3201 is a medium-severity vulnerability in inspireui MStore API – Create Native Android \u0026 iOS Apps On The Cloud, published on 14 Jun 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-3201 and fix it if it is affected.\n\nWhat it is: CVE-2023-3201 is a medium-severity vulnerability in inspireui MStore API – Create Native Android \u0026 iOS Apps On The Cloud, published on 14 Jun 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-3201 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-2023-3201/ (Markdown: https://insights.sbomify.com/CVE-2023-3201/index.md)","id":"CVE-2023-3201","markdown":"https://insights.sbomify.com/CVE-2023-3201/index.md","name":"CVE-2023-3201","record":{"aliases":["GHSA-fg8x-c2rv-v75q"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can trick administrators into updating order titles via forged requests due to missing nonce validation in the MStore API plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"mstore_api","vendor":"inspireui"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The MStore API plugin for WordPress is vulnerable to Cross-Site Request Forgery due to missing nonce validation on the mstore_update_new_order_title function. This makes it possible for unauthenticated attackers to update new order title via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.","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= 3.9.6 - Cross-Site Request Forgery to Order Title Update","id":"CVE-2023-3201","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"MStore API \u003c= 3.9.6 - Cross-Site Request Forgery to Firebase Server Key Update","id":"CVE-2023-3202"},"packages":[],"prev":{"headline":"MStore API \u003c= 3.9.6 - Cross-Site Request Forgery to Order Message Update","id":"CVE-2023-3200"},"products":["MStore API – Create Native Android \u0026 iOS Apps On The Cloud"],"published":"2023-06-14","related":[{"cvss_score":9.8,"headline":"MStore API – Create Native Android \u0026 iOS Apps On The Cloud \u003c= 4.14.7 - Authentication Bypass","id":"CVE-2024-6328","kev_date_added":null,"published":"2024-07-12"},{"cvss_score":9.8,"headline":"MStore API \u003c= 4.10.7 - Unauthorized Account Access and Privilege Escalation","id":"CVE-2023-3277","kev_date_added":null,"published":"2023-11-03"},{"cvss_score":9.8,"headline":"MStore API \u003c 3.9.9 - Unauthenticated Privilege Escalation","id":"CVE-2023-3076","kev_date_added":null,"published":"2023-07-10"},{"cvss_score":9.8,"headline":"MStore API \u003c 3.9.8 - Unauthenticated Blind SQLi","id":"CVE-2023-3077","kev_date_added":null,"published":"2023-07-10"},{"cvss_score":9.8,"headline":"MStore API \u003c= 4.0.1 - Unauthenticated SQL Injection","id":"CVE-2023-3197","kev_date_added":null,"published":"2023-06-24"},{"cvss_score":9.8,"headline":"MStore API \u003c= 2.1.5 - Authentication Bypass","id":"CVE-2020-36713","kev_date_added":null,"published":"2023-06-07"},{"cvss_score":9.8,"headline":"MStore API \u003c= 3.9.2 - Authentication Bypass","id":"CVE-2023-2732","kev_date_added":null,"published":"2023-05-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-08","vendors":["inspireui"]},"summary":"Unauthenticated attackers can trick administrators into updating order titles via forged requests due to missing nonce validation in the MStore API plugin.","url":"https://insights.sbomify.com/CVE-2023-3201/"}