SQL Injection in craftcms/commerce (CVE-2026-32272)
Summary
SQL injection in craftcms/commerce (CVE-2026-32272). Risk of unauthorized operations or information disclosure. Exploitable via ElementIndexesController. Mitigation: upgrade to 5.6.0 or later.
Original description
The description as published by the source.
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.
Impact
- Full database read access via blind SQL injection
- Privilege escalation via security key extraction → forged admin sessions
Prerequisites
- Authenticated control panel user
- Commerce plugin installed
- Products with variants in the database
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-32272 has been found in craftcms/commerce.
Attackers can target a specific entry point like ElementIndexesController over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade craftcms/commerce to 5.6.0 or later.
If unsure, ask your IT team or search "craftcms/commerce CVE-2026-32272" on the vendor's site.
CVE-2026-32272 (craftcms/commerce) — CWE-89
Attack surface: ElementIndexesController / where / orderBy / hasVariant
Patched: 5.6.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SQL injection (CWE-89) exists in craftcms/commerce. Attackers reach the vulnerable code path via ElementIndexesController.
Check the vendor advisory for the affected versions of craftcms/commerce. Attack surface: ElementIndexesController / where / orderBy / hasVariant.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 5.6.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'craftcms/commerce' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'craftcms/commerce' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
craftcms/commerceを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade craftcms/commerce to 5.6.0ステージング環境で 5.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com