Strategic Overview
- Status
- Patched in 4.0.2
- Affected Plugin
- MStore API – Create Native Android & iOS Apps On The Cloud
- Affected Version
<= 4.0.1- CVSS
- 9.8Critical
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2023-3197
At a glance
CVE-2023-3197 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the MStore API WordPress plugin, affecting versions <= 4.0.1. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 4.0.2; sites on affected versions should update now. Disclosed June 2023, reported by Truoc Phan.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Reaching this weakness in MStore API <= 4.0.1 takes no account at all. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For MStore API the fix is 4.0.2: builds <= 4.0.1 are affected, anything from 4.0.2 onward is not.
Remediation
Update to version 4.0.2, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: MStore API 4.0.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in MStore API – Create Native Android & iOS Apps On The Cloud
- 9.8CVE-2026-13447: MStore API <= 4.20.0 Authentication Bypass
CVE-2026-13447 - 9.8CVE-2026-27543: MStore API Privilege Escalation
CVE-2026-27543 - 9.8CVE-2024-6328: MStore API Authentication Bypass
CVE-2024-6328 - 9.8CVE-2023-3277: MStore API Unauthorized Account Access and Privilege
CVE-2023-3277 - 9.8CVE-2023-3076: MStore API <= 3.9.8 Privilege Escalation
CVE-2023-3076 - 9.8CVE-2023-2732: MStore API <= 3.9.2 Authentication Bypass
CVE-2023-2732 - 9.8CVE-2023-2734: MStore API <= 3.9.1 Authentication Bypass
CVE-2023-2734 - 9.8CVE-2023-2733: MStore API <= 3.9.0 Authentication Bypass
CVE-2023-2733
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C