Skip to main content
VulnerabilityPublished

CVE-2026-29172: craftcms commerce · SQL Injection

Affects craftcms commerceSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 5.5.3 or 4.10.2 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.5.3, 4.10.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade commerce and craftcms/commerce to 5.5.3 or 4.10.2.

Affected software

ProductAffectedFixed in
craftcmscommerceAffected
  • >=5.0.0 <5.5.3
Fixed in
  • 5.5.3
craftcmscommerceAffected
  • >=4.0.0 <4.10.2
Fixed in
  • 4.10.2
GitHubcraftcms/commercepkg:github/craftcms/commerceOther threatsAffected
  • <4.10.2
  • >=4.0.0 <4.10.2
  • <5.5.3
  • >=5.0.0 <5.5.3
Fixed in
  • 4.10.2
  • 5.5.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-29172, organizations should immediately upgrade Craft Commerce to versions 4.10.2 or 5.5.3 where the vulnerability is patched. If immediate upgrade is not possible, implement strict input validation and sanitization on the 'sort' parameter to enforce a whitelist of allowed column names before passing values to orderBy(). Employ web application firewalls (WAFs) with custom rules to detect and block suspicious SQL injection patterns targeting the ORDER BY clause. Limit and monitor authenticated user privileges to reduce the risk of credential abuse. Conduct regular security audits and penetration testing focusing on injection flaws. Enable detailed logging and alerting on database query anomalies. Educate developers on secure coding practices, especially regarding dynamic query construction and the risks of unsanitized input. Finally, maintain an incident response plan to quickly address any suspected exploitation.

Description

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.

References

Community reviews

Loading reviews…