CVE-2026-29174
SQL Injection in Craft Commerce Inventory Leads to Database Compromise
Publication date: 2026-03-10
Last updated on: 2026-03-11
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| craftcms | craft_commerce | From 5.0.0 (inc) to 5.5.3 (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?
This vulnerability affects Craft Commerce, an ecommerce platform for Craft CMS, in versions prior to 5.5.3. It is a SQL Injection vulnerability in the inventory levels table data endpoint. Specifically, the parameters sort[0][direction] and sort[0][sortField] are used directly in a database query's addOrderBy() clause without any validation or sanitization. An authenticated attacker with access to the Commerce Inventory section can exploit this to inject arbitrary SQL queries.
This can potentially lead to a full compromise of the database.
How can this vulnerability impact me? :
If exploited, this vulnerability can allow an attacker to execute arbitrary SQL commands on the database. This could lead to unauthorized access, modification, or deletion of sensitive data stored in the database.
Ultimately, it can result in a full database compromise, which may disrupt business operations, cause data loss, and expose confidential information.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade Craft Commerce to version 5.5.3 or later, where the SQL Injection issue in the inventory levels table data endpoint has been fixed.
Additionally, ensure that only authenticated users with proper permissions can access the Commerce Inventory section to reduce the risk of exploitation.