Is CVE-2026-32272 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-32272 being exploited in the wild.

How severe is CVE-2026-32272?

High severity, with a CVSS score of 4, published 13 April 2026.

Which products and versions are affected?

craftcms/commerce (Packagist) >= 5.0.0, < 5.6.0, ECOSYSTEM:introduced=5.0.0,fixed=5.6.0.

Is there a fix for CVE-2026-32272?

Yes. craftcms/commerce (Packagist): upgrade to 5.6.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-32272 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-32272?

Check whether you run craftcms/commerce (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-32272: Craft CMS Commerce SQL injection in Product and Variant queries

Q: Is there a fix for CVE-2026-32272?

Yes. craftcms/commerce (Packagist): upgrade to 5.6.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-32272 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-32272?

Check whether you run craftcms/commerce (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-32272 · Severity: high · CVSS 4 · Published 2026-04-13

Craft Commerce, an e-commerce platform for Craft CMS, is vulnerable to a security flaw that allows authorized users with control panel access to extract sensitive information from the database. By exploiting this vulnerability, an attacker could gain full access to customer data or escalate their own privileges to become a full administrator. This could lead to a complete compromise of the online store and its underlying data.

Technologies: craftcms/commerce (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2026-32272 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-32272 being exploited in the wild.
How severe is CVE-2026-32272?: High severity, with a CVSS score of 4, published 13 April 2026.
Which products and versions are affected?: craftcms/commerce (Packagist) >= 5.0.0, < 5.6.0, ECOSYSTEM:introduced=5.0.0,fixed=5.6.0.
Is there a fix for CVE-2026-32272?: Yes. craftcms/commerce (Packagist): upgrade to 5.6.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-32272 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-32272?: Check whether you run craftcms/commerce (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

craftcms/commerce (Packagist): upgrade to 5.6.0 or later
```
composer require craftcms/commerce:^5.6.0
```

Technical details

A blind SQL injection vulnerability exists in Craft Commerce due to improper sanitization of the 'hasVariant' and 'hasProduct' properties within ProductQuery and VariantQuery. While top-level Yii2 Query properties were previously blocklisted in ElementIndexesController, these specific subquery properties bypass the filter and are passed to Craft::configure() without validation. An authenticated control panel user can exploit this by injecting SQL into the 'where' clause of these subqueries (e.g., via criteria[hasVariant][where]=...). This allows for boolean-based blind SQL injection to extract arbitrary database data, including security keys used for session forgery. The issue is fixed in version 5.6.0.

Affected products

Craft CMS Commerce >= 5.0.0, < 5.6.0

Identifiers

CVE-2026-32272
GHSA-r54v-qq87-px5r

Timeline

2026-04-13: patched: Fixed in version 5.6.0
2026-04-14: disclosed: GitHub Advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.