Summary
Craft Commerce hasVariant/hasProduct Blind SQL Injection
Overview
Craft Commerce’s ProductQuery::hasVariant and VariantQuery::hasProduct properties bypass the unset() blocklist added to ElementIndexesController in GHSA-2453-mppf-46cj.
The blocklist only strips top-level Yii2 Query properties (where, orderBy, etc.), but hasVariant and hasProduct pass
through untouched. Internally, these properties call Craft::configure() on a subquery without sanitization, re-introducing SQL injection via criteria[hasVariant][where]=INJECTED_SQL.
An authenticated control panel user can perform boolean-based blind SQL injection through the patched ElementIndexesController and extract arbitrary database contents.
Prerequisites
- Authenticated control panel user
- Commerce plugin installed
- Products with variants in the database
Impact
- Full database read access via blind SQL injection
- Privilege escalation via security key extraction → forged admin sessions
Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-32272? CVE-2026-32272 is a high-severity SQL injection vulnerability in craftcms/commerce (composer), affecting versions >= 5.0.0, < 5.6.0. It is fixed in 5.6.0. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
- Which versions of craftcms/commerce are affected by CVE-2026-32272? craftcms/commerce (composer) versions >= 5.0.0, < 5.6.0 is affected.
- Is there a fix for CVE-2026-32272? Yes. CVE-2026-32272 is fixed in 5.6.0. Upgrade to this version or later.
- Is CVE-2026-32272 exploitable, and should I be worried? Whether CVE-2026-32272 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-32272 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-32272? Upgrade
craftcms/commerceto 5.6.0 or later.