# CVE-2026-32271: Craft Commerce: SQL Injection can lead to Remote Code Execution via TotalRevenue Widget

> Authenticated users can achieve remote code execution via SQL injection in the TotalRevenue widget, allowing arbitrary command execution.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Apr 2026
- **Updated:** 16 Apr 2026
- **Also known as:** GHSA-875v-7m49-8x88

## What is CVE-2026-32271?

CVE-2026-32271 is a high-severity SQL injection vulnerability in craftcms commerce, published on 13 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Craft Commerce is an ecommerce platform for Craft CMS. In versions 4.0.0 through 4.10.2 and 5.0.0 through 5.5.4, there is an SQL injection vulnerability in the Commerce TotalRevenue widget which allows any authenticated control panel user to achieve remote code execution through a four-step exploitation chain. The attack exploits unsanitized widget settings interpolated into SQL expressions, combined with PDO's default multi-statement query support, to inject a maliciously serialized PHP object into the queue table. When the queue consumer processes the injected job, the unrestricted unserialize() call in yii2-queue instantiates a GuzzleHttp FileCookieJar gadget chain whose __destruct() method writes a PHP webshell to the server's webroot. The complete chain requires only three HTTP requests, no administrative privileges, and results in arbitrary command execution as the PHP process user, with queue processing triggered via an unauthenticated endpoint. This issue has been fixed in versions 4.10.3 and 5.5.5.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-32271?

4 open source packages ship an affected version, including craftcms/commerce.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `craftcms/commerce` | Packagist | From 4.0.0 | 4.10.3 |
| `craftcms/commerce` | Packagist | From 4.0.0 | 4.10.3 |
| `craftcms/commerce` | Packagist | From 5.0.0 | 5.5.5 |
| `craftcms/commerce` | Packagist | From 5.0.0 | 5.5.5 |

## How do I fix CVE-2026-32271?

Upgrade craftcms/commerce to a fixed version for your release line: 4.10.3 or 5.5.5.

## Is CVE-2026-32271 being exploited?

There is no known exploitation of CVE-2026-32271 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32271 and fix it if it is affected.

What it is: CVE-2026-32271 is a high-severity SQL injection vulnerability in craftcms commerce, published on 13 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-32271 in the wild and no public exploit code.

Affected packages and fixed versions:
- craftcms/commerce (Packagist): affected from 4.0.0; fixed in 4.10.3
- craftcms/commerce (Packagist): affected from 4.0.0; fixed in 4.10.3
- craftcms/commerce (Packagist): affected from 5.0.0; fixed in 5.5.5
- craftcms/commerce (Packagist): affected from 5.0.0; fixed in 5.5.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32271/ (Markdown: https://insights.sbomify.com/CVE-2026-32271/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32271
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32271
- OSV: https://osv.dev/vulnerability/CVE-2026-32271

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32271/
Summaries are generated and may contain mistakes; the official description above is the record.