CVE-2021-47909
SQL Injection in Multi-E-Cart Ultimate 2.4 Admin Modules
Publication date: 2026-02-01
Last updated on: 2026-02-03
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| techraft | mult-e-cart_ultimate | to 2.5 (exc) |
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
Can you explain this vulnerability to me?
CVE-2021-47909 is a high-severity SQL injection vulnerability in Mult-E-Cart Ultimate version 2.4. It affects multiple modules including inventory, customer, vendor, and order management. Remote attackers who have privileged vendor or admin roles can exploit the 'id' parameter in HTTP requests to inject and execute malicious SQL commands. This happens because the application does not properly sanitize the 'id' parameter and lacks the use of prepared statements, allowing attackers to manipulate SQL queries and potentially compromise the database management system. [2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to full compromise of the database management system, web server, and web application. Attackers can execute arbitrary SQL commands, which may result in unauthorized access to sensitive data, data manipulation, and loss of data integrity. Since the vulnerability requires privileged vendor or admin roles, attackers with such access can leverage it to escalate their control and cause significant damage to the system. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'id' parameter in the affected modules (inventory, customer, vendor, order) for SQL injection using specially crafted HTTP GET requests. Example payloads include union-based SQL injection strings such as: 1' union select 1,2,3,4,@@version--&edit=t or 1' union select 1,2,3,4,@@database--&edit=t. Example vulnerable URLs to test are: /inventory/inventory/update?id=1' union select 1,2,3,4,5--&edit=t, /customer/customer/view?id=1' union select 1,2,3,4,5--&edit=t, /vendor/vendor/view?id=1' union select 1,2,3,4,5--&edit=t, and /order/sub-order/view-order?id=' union select 1,2,3,4,5. You can use curl commands to send these requests and observe SQL errors or unexpected responses indicating injection points. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Disabling SQL error display for non-admin users or logging errors outside the UI to prevent information leakage. 2) Using prepared statements in the application code to prevent SQL injection. 3) Restricting the 'id' parameter to disallow special characters in GET and POST requests. 4) Encoding and escaping the 'id' parameter content on GET requests to ensure safe input handling. [2]