Black Friday60% off BLACKFRIDAY2026
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
critical·Product Based Web Vulnerabilities·Updated Oct 8, 2024

CVE-2023-3077 Scanner

CVE-2023-3077 Scanner - SQL Injection (SQLi) vulnerability in MStore API WordPress Plugin

Est. Time~1 minutes
Scan TypeSingle Scan
Targetsdomain, ipv4, subdomain
CostFree
2.7k
Times Used
continuous scan runs
4.2k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
9.8
CVSS
Description

The MStore API WordPress plugin before 3.9.8 does not sanitise and escape a parameter before using it in a SQL statement, leading to a Blind SQL injection exploitable by unauthenticated users. This is only exploitable if the site owner elected to pay to get access to the plugins' pro features, and uses the woocommerce-appointments plugin.

Attack Vector
-
Privileges Req.
-
User Interaction
-
Affected
MStore API
AFFECTED< 3.9.8→SAFE ✓≥ 3.9.8
Updated Nov 7, 2026View on NVD →
Detail

MStore API is a widely used WordPress plugin designed to integrate modern mobile applications with WordPress-based e-commerce websites. It provides seamless connections between mobile applications and e-commerce stores, allowing efficient management and synchronization of product data and orders. Businesses and developers utilize this plugin for creating interactive and real-time mobile solutions. The API is often employed by companies aiming to expand their online presence through mobile commerce. It facilitates operations by allowing mobile apps to communicate with the WordPress database securely. MStore API is an essential tool for those seeking to bridge the gap between mobile applications and WordPress-driven e-commerce solutions.

SQL Injection vulnerabilities like the one in MStore API occur when untrusted input is transmitted to an SQL query, allowing attackers to interfere with the application's query execution. This vulnerability, specifically a Blind SQL Injection, affects the 'product_id' parameter and is critical because it allows for unauthorized data retrieval from the database. Attackers can exploit this to extract sensitive information without having direct access to the data. The accessibility of this vulnerability makes it a popular target among cybercriminals. With high potential impacts, SQL Injection attacks can severely compromise data integrity and security. Recognizing and patching such vulnerabilities is crucial for maintaining a secure application ecosystem.

The MStore API version below 3.9.8 is vulnerable to Blind SQL Injection via its 'product_id' parameter. An attacker can exploit this flaw by sending a specially crafted query to the vulnerable endpoint, causing an unintended execution of SQL commands. This manipulation is possible due to insufficient input validation, leading to unauthorized data access. The endpoint vulnerable to attack is '/wp-json/api/flutter_booking/get_staffs?product_id='. By using payloads that alter normal SQL queries, attackers can force the database to execute malicious commands, potentially accessing, modifying, or deleting data. The blind nature of this SQL Injection requires timing or error-based methods to extract data due to the absence of direct feedback from commands.

Exploitation of this SQL Injection vulnerability can lead to serious security breaches, including unauthorized disclosure of confidential information, such as user credentials and personal data. The attacker might alter or delete records, compromise the integrity of the system, and escalate their privileges by executing further attacks. Such vulnerabilities undermine trust in the application and can cause lasting reputational damage. Additionally, attackers might gain further access to network resources, paving the way for more severe compromises. Therefore, swift remediation and regular security checks are critical to safeguarding the system from such vulnerabilities.

REFERENCES

Solution Advice
  • Update the MStore API WordPress Plugin to version 3.9.8 or later.
  • Employ prepared statements and parameterized queries to prevent SQL Injection.
  • Utilize input validation and sanitization to ensure all inputs are thoroughly checked before being processed.
  • Regularly audit and test for security vulnerabilities within the application's codebase.
  • Enable logging and monitoring to detect any suspicious activity that may indicate an exploitation attempt.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

12,000+ scanners. Free to start. No credit card required.