CVE-2024-58341
SQL Injection in OpenCart 4.0.2.3 Enables Data Extraction
Publication date: 2026-03-25
Last updated on: 2026-03-27
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| opencart | opencart | 4.0.2.3 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided context and resources do not contain specific information regarding how this SQL injection vulnerability in OpenCart Core 4.0.2.3 affects compliance with common standards and regulations such as GDPR or HIPAA.
Can you explain this vulnerability to me?
This vulnerability is a SQL injection issue found in OpenCart Core version 4.0.2.3. It allows attackers who are not authenticated to manipulate database queries by injecting malicious SQL code through the 'search' parameter in the product search endpoint.
Attackers can send specially crafted GET requests with malicious 'search' values to exploit this vulnerability. They can use techniques such as boolean-based blind or time-based blind SQL injection to extract sensitive information from the database.
How can this vulnerability impact me? :
This vulnerability can have serious impacts including unauthorized access to sensitive database information. Since attackers can extract data without authentication, it can lead to data breaches, exposure of confidential information, and potential compromise of the integrity of the database.
The CVSS v3.1 base score of 8.2 indicates a high severity, meaning the vulnerability is relatively easy to exploit remotely without any privileges or user interaction, and it can result in a high impact on confidentiality.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by testing the 'search' parameter of the product search endpoint for injection flaws.
A practical method is to use sqlmap, an automated SQL injection tool, with a command targeting the vulnerable parameter.
- sqlmap -u "http://127.0.0.1/index.php?route=product/search&search=#1" --level=5 --risk=3 -p search --dbs
This command tests the 'search' parameter for SQL injection by attempting to enumerate databases using boolean-based and time-based blind SQL injection techniques.
What immediate steps should I take to mitigate this vulnerability?
The provided resources do not specify explicit immediate mitigation steps such as patches or configuration changes for this vulnerability.
However, since the vulnerability is a SQL injection in the 'search' parameter of OpenCart Core 4.0.2.3 and earlier, immediate general mitigation steps include:
- Restrict or disable access to the product search endpoint if possible until a fix is applied.
- Implement web application firewall (WAF) rules to detect and block malicious SQL injection payloads targeting the 'search' parameter.
- Monitor logs for suspicious GET requests containing unusual or crafted 'search' parameter values.
- Plan to upgrade OpenCart to a version that addresses this vulnerability once an official patch or update is released.