What is the CVSS score of CVE-2026-29174?

CVE-2026-29174 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

Is there a public PoC exploit available for CVE-2026-29174?

Yes, a public proof-of-concept exploit is available for CVE-2026-29174. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2026-29174?

Within 24 hours: Identify all systems running Craft Commerce and determine current versions; isolate or restrict network access to affected instances if on versions prior to 5.5.3. Within 7 days: Apply vendor patch to upgrade all instances to version 5.5.3 or later; validate patch deployment in production. Within 30 days: Conduct database audit to identify any unauthorized access or data manipulation; review access logs for suspicious inventory endpoint activity.

Craft Commerce CVE-2026-29174

HIGH

SQL Injection (CWE-89)

2026-03-10 security-advisories@github.com

GHSA-pmgj-gmm4-jh6j

SQLi Craft Commerce Craftcms

8.8

CVSS 3.1 · GitHub Advisory

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Authenticate to Craft Commerce admin panel
Delivery

Access inventory levels data endpoint
Exploit

Inject malicious SQL in sort parameters
Execution

Execute arbitrary database queries
Impact

Extract or modify sensitive data

Vulnerability Assessment

Weakness	CWE CWE-89 OWASP Top 10:2025 A05:2025 - Injection ASVS 5.0 V1 - Encoding and Sanitization Parameterized queries, prepared statements MITRE ATT&CK 2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Exploitation Conditions	Authenticated user account with explicit access to Commerce Inventory section required. Vulnerable versions: Craft Commerce prior to 5.5.3. The sort[0][direction] and sort[0][sortField] parameters must be exposed in the inventory levels table data endpoint without input validation.
Impact	CVSS 8.8 (HIGH). Attack vector: Network. Complexity: Low. Privileges required: Low. User interaction: None. Exploitation requires authentication. Public exploit/POC available.
Exploit ScenarioDerived	An attacker (requires authentication) could exploit this flaw, a full database compromise.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

Craft Commerce versions prior to 5.5.3 contain an SQL injection vulnerability in the inventory levels endpoint where sort parameters are improperly sanitized, allowing authenticated users with Commerce Inventory access to execute arbitrary database queries. Public exploit code exists for this vulnerability, which could enable complete database compromise. Update to version 5.5.3 or later to resolve this high-severity issue.

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 21:55 CVSS 8.8

Craft Commerce is an ecommerce platform for Craft CMS. Prior to 5.5.3, Craft Commerce is vulnerable to SQL Injection in the inventory levels table data endpoint. [CVSS 8.8 HIGH]

RemediationAI

A vendor patch is available — apply it immediately. Fixed in version 5.5.3.. Use parameterized queries. Implement input validation. Restrict network access to the affected service where possible.

Affected Packages

composer craftcms/commerce fix: 5.5.3

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in composer

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Classified as CWE-89 (SQL Injection). Affects the inventory levels table data component of Craft Commerce. Craft Commerce is an ecommerce platform for Craft CMS. Prior to 5.5.3, Craft Commerce is vulnerable to SQL Injection in the inventory levels table data endpoint. The sort[0][direction] and sort[0][sortField] parameters are concatenated directly into an addOrderBy() clause without any validation or sanitization. An authenticated attacker with access to the Commerce Inventory section can inject arbitrary SQL queries, potentially leading to a full database compromise. This vulnerability is fixed in

Know when Craft Commerce gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 8.8 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

PoC Detected

Mar 11, 2026 - 16:55 vuln.today

Public exploit code

Patch released

Mar 11, 2026 - 16:55 nvd

Patch available

CVE Published

Mar 10, 2026 - 20:16 nvd

HIGH 8.8

DescriptionGitHub Advisory

Craft Commerce is an ecommerce platform for Craft CMS. Prior to 5.5.3, Craft Commerce is vulnerable to SQL Injection in the inventory levels table data endpoint. The sort[0][direction] and sort[0][sortField] parameters are concatenated directly into an addOrderBy() clause without any validation or sanitization. An authenticated attacker with access to the Commerce Inventory section can inject arbitrary SQL queries, potentially leading to a full database compromise. This vulnerability is fixed in 5.5.3.

Executive ViewAI

Why It Matters

Craft Commerce versions prior to 5.5.3 contain a critical SQL injection vulnerability in the inventory management endpoint that could allow attackers to access, modify, or exfiltrate sensitive database information including customer data and transaction records. Organizations running affected versions face immediate risk of data breach and operational disruption.

Business Impact: High

Compensating Controls

Apply vendor patch. If immediate patching is not possible: implement Web Application Firewall (WAF) rules to block SQL injection patterns on inventory endpoints; restrict API access to inventory levels endpoint via network ACLs to trusted IP ranges only; disable inventory management API if not actively used; enable comprehensive logging and monitoring on database query patterns.

Threat Intelligence Overview

EPSS Score

0.0%

Top 99% exploitable

Exploit

POC

Public exploit code exists

Data Quality

5 sources

Confidence: Medium

NVD

CVE.org

EPSS

GitHub

VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC Yes

EPSS 0.0%

Patch available Yes

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.