{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-3197 exists.","fix":"No fix has been published for CVE-2023-3197 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-3197 is a critical SQL injection vulnerability in inspireui MStore API – Create Native Android \u0026 iOS Apps On The Cloud, published on 24 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-3197 and fix it if it is affected.\n\nWhat it is: CVE-2023-3197 is a critical SQL injection vulnerability in inspireui MStore API – Create Native Android \u0026 iOS Apps On The Cloud, published on 24 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-3197 exists.\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-3197/ (Markdown: https://insights.sbomify.com/CVE-2023-3197/index.md)","id":"CVE-2023-3197","markdown":"https://insights.sbomify.com/CVE-2023-3197/index.md","name":"CVE-2023-3197","record":{"aliases":["GHSA-3xv2-fg82-8w4g"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can exploit SQL injection in the MStore API plugin to extract sensitive database information.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"mstore_api","vendor":"inspireui"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"The MStore API plugin for WordPress is vulnerable to Unauthenticated Blind SQL Injection via the 'id' parameter in versions up to, and including, 4.0.1 due to insufficient escaping on the user supplied parameters and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2023/CVE-2023-3197.yaml","stars":null,"title":"WordPress MStore API \u003c= 4.0.1 - Unauthenticated SQL Injection"}],"tier":"weaponised"},"has_fix":null,"headline":"MStore API \u003c= 4.0.1 - Unauthenticated SQL Injection","id":"CVE-2023-3197","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"MStore API \u003c= 3.9.6 - Cross-Site Request Forgery to Order Status Update","id":"CVE-2023-3198"},"packages":[],"prev":{"headline":"Multiple vulnerabilities in Canopsis of Capensis","id":"CVE-2023-3196"},"products":["MStore API – Create Native Android \u0026 iOS Apps On The Cloud"],"published":"2023-06-24","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= 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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["inspireui"]},"summary":"Unauthenticated attackers can exploit SQL injection in the MStore API plugin to extract sensitive database information.","url":"https://insights.sbomify.com/CVE-2023-3197/"}