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

CVE-2026-29172 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-29172?

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

How to fix or mitigate CVE-2026-29172?

Within 24 hours: Identify all Craft Commerce instances and confirm versions. Within 7 days: Apply vendor patches (upgrade to 4.10.2 or 5.5.3+) to all affected systems. Within 30 days: Conduct security audit of database access logs and implement compensating controls if patching is delayed.

Craft Commerce CVE-2026-29172

HIGH

SQL Injection (CWE-89)

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

GHSA-j3x5-mghf-xvfw

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
Delivery

Craft malicious sort parameter with SQL injection
Exploit

Pass unsanitized column name to orderBy()
Execution

Execute arbitrary SQL in ORDER BY clause
Impact

Extract or modify database 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 access to Craft Commerce purchasables table endpoint required. Craft Commerce versions prior to 4.10.2 (4.x branch) or 5.5.3 (5.x branch). The sort parameter must be accepted by the endpoint without whitelist validation on column names.
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 vulnerability to compromise the affected system.

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

SQL injection in Craft Commerce's purchasables endpoint allows authenticated attackers to manipulate the sort parameter and execute arbitrary SQL queries via the unvalidated ORDER BY clause. Versions prior to 4.10.2 and 5.5.3 are vulnerable, with public exploit code available. An attacker with valid credentials can extract sensitive database information or modify data without additional user interaction.

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 4.10.2 and 5.5.3, Craft Commerce is vulnerable to SQL Injection in the purchasables table endpoint. [CVSS 8.8 HIGH]

RemediationAI

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

Affected Packages

composer craftcms/commerce fix: 4.10.2, 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 purchasables table component of Craft Commerce. Craft Commerce is an ecommerce platform for Craft CMS. Prior to 4.10.2 and 5.5.3, Craft Commerce is vulnerable to SQL Injection in the purchasables table endpoint. The sort parameter is split by | and the first part (column name) is passed directly as an array key to orderBy() without whitelist validation. Yii2's query builder does NOT escape array keys, allowing an authenticated attacker to inject arbitrary SQL into the ORDER BY clause. This vulnerability is fixed in 4.10.2 and 5.5.3.

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:54 vuln.today

Public exploit code

Patch released

Mar 11, 2026 - 16:54 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 4.10.2 and 5.5.3, Craft Commerce is vulnerable to SQL Injection in the purchasables table endpoint. The sort parameter is split by | and the first part (column name) is passed directly as an array key to orderBy() without whitelist validation. Yii2's query builder does NOT escape array keys, allowing an authenticated attacker to inject arbitrary SQL into the ORDER BY clause. This vulnerability is fixed in 4.10.2 and 5.5.3.

Executive ViewAI

Why It Matters

Craft Commerce installations are vulnerable to SQL injection attacks through the purchasables table endpoint, potentially allowing attackers to extract sensitive data including customer information and payment records. Organizations running affected versions (pre-4.10.2 or pre-5.5.3) should prioritize immediate patching to prevent data breaches and regulatory compliance violations.

Business Impact: High

Compensating Controls

Apply vendor patch. If immediate patching is not feasible: implement WAF rules to block SQL injection patterns in purchasables endpoint requests, restrict database account permissions using principle of least privilege, enable database activity monitoring and alerting, and disable public access to the purchasables endpoint if not business-critical.

Threat Intelligence Overview

EPSS Score

0.0%

Top 93% 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.