Skip to main content
VulnerabilityPublished

CVE-2026-29174: 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 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 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.5.3
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.

Affected software

ProductAffectedFixed in
craftcmscommerceAffected
  • >=5.0.0 <5.5.3
Fixed in
  • 5.5.3
GitHubcraftcms/commercepkg:github/craftcms/commerceOther threatsAffected
  • <5.5.3 >=5.0.0
Fixed in
  • 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

  1. Immediate upgrade to Craft Commerce version 5.5.3 or later, where the vulnerability is fixed, is the most effective mitigation.
  2. Restrict access to the Commerce Inventory section strictly to trusted and necessary personnel to reduce the attack surface.
  3. Implement strong authentication mechanisms, including multi-factor authentication, to prevent unauthorized access to authenticated areas.
  4. Monitor logs for unusual or suspicious activity related to inventory sorting parameters or database queries.
  5. Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the affected parameters.
  6. Conduct regular security audits and code reviews to identify and remediate similar unsafe coding practices.
  7. Backup databases regularly and ensure backups are secure to enable recovery in case of compromise.
  8. Educate developers and administrators about secure coding and the risks of unsanitized input concatenation in SQL queries.

Description

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.

References

Community reviews

Loading reviews…