8.7

CVSS Score

4.0

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2026-32272

CVE-2026-32272: Craft Commerce: Blind SQL Injection via hasVariant/hasProduct

Craft Commerce is an ecommerce platform for Craft CMS. In versions 5.0.0 through 5.5.4, an SQL injection vulnerability exists where the ProductQuery::hasVariant and VariantQuery::hasProduct properties bypass the input sanitization blocklist added to ElementIndexesController in a prior security fix (GHSA-2453-mppf-46cj). The blocklist only strips top-level Yii2 Query properties such as where and orderBy, but hasVariant and hasProduct pass through untouched and internally call Craft::configure() on a subquery without sanitization, re-introducing SQL injection. Any authenticated control panel user can exploit this via boolean-based blind SQL injection to extract arbitrary database contents, including security keys that enable forging admin sessions for privilege escalation. This issue has been fixed in version 5.6.0.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2026-32272

CVE-2026-32272:

8.7

CVSS Score

4.0

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
craftcms/commerce	composer	>= 5.0.0, < 5.6.0	5.6.0

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability is a blind SQL injection in Craft Commerce, specifically within the product and variant element queries. The root cause is that the hasVariant property on ProductQuery and the hasProduct property on VariantQuery did not sanitize their input before using it to configure a sub-query. A previous fix for a similar vulnerability (GHSA-2453-mppf-46cj) only sanitized top-level query properties, but these nested properties bypassed the blocklist.

An authenticated control panel user could exploit this by sending a crafted request to endpoints that use these queries, such as the element listing pages (/admin/commerce/products). By embedding a malicious SQL statement in the where parameter of the hasVariant or hasProduct criteria (e.g., criteria[hasVariant][where]=...SQL...), they could execute arbitrary SQL queries.

The patch addresses this by introducing a new helper method, craft\commerce\helpers\ProductQueryHelper::cleanseQueryCriteria(). This method is now called within _applyHasVariantParam and _applyHasProductParam to sanitize the criteria array before it's passed to Craft::configure(). The cleanseQueryCriteria method, in turn, leverages Craft CMS's core ElementHelper::cleanseQueryCriteria if the request is coming from a relevant controller (like ElementIndexesController), effectively stripping out dangerous keys like where and orderBy from the user-provided criteria and preventing the injection.

Vulnerable functions

craft\commerce\elements\db\ProductQuery::_applyHasVariantParam

src/elements/db/ProductQuery.php

The `_applyHasVariantParam` method was vulnerable to SQL injection because it used the `hasVariant` property, which can be controlled by a user, to configure a new `Variant` query via `Craft::configure()` without prior sanitization. An attacker could craft a request to the element index listing that included a malicious `where` clause within the `hasVariant` criteria, leading to blind SQL injection. The patch mitigates this by first passing the criteria through the new `ProductQueryHelper::cleanseQueryCriteria()` function.

craft\commerce\elements\db\VariantQuery::_applyHasProductParam

src/elements/db/VariantQuery.php

The `_applyHasProductParam` method was vulnerable to SQL injection because it used the `hasProduct` property, which can be controlled by a user, to configure a new `Product` query via `Craft::configure()` without prior sanitization. Similar to the `hasVariant` vulnerability, an attacker could inject a malicious `where` clause into the `hasProduct` criteria to perform blind SQL injection. The patch fixes this by sanitizing the criteria using `ProductQueryHelper::cleanseQueryCriteria()` before it is used.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.