# CVE-2026-32270: Craft Commerce has an unauthenticated information disclosure that can leak some customer order data on anonymous payments

> Unauthenticated attackers can leak sensitive customer order data, including emails and addresses, via the anonymous payment endpoint.

- **Severity:** Low 1.7 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Apr 2026
- **Updated:** 14 Apr 2026
- **Also known as:** GHSA-3vxg-x5f8-f5qf

## What is CVE-2026-32270?

CVE-2026-32270 is a low-severity vulnerability in craftcms commerce, published on 13 Apr 2026. An attacker can exploit it over the internet without logging in, 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, the PaymentsController::actionPay discloses some order data to unauthenticated users when an order number is provided and the email check fails during an anonymous payment. The JSON error response includes the serialized order object (order), which contains some sensitive fields such as customer email, shipping address, and billing address. The frontend payment flow's actionPay() retrieves orders by number before authorization is fully enforcedLoad order by number. This issue has been fixed in versions 4.11.0 and 5.6.0.

Weakness: CWE-862 (Missing Authorization), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `craftcms/commerce` | Packagist | From 4.0.0 | 4.11.0 |
| `craftcms/commerce` | Packagist | From 4.0.0 | 4.11.0 |
| `craftcms/commerce` | Packagist | From 5.0.0 | 5.6.0 |
| `craftcms/commerce` | Packagist | From 5.0.0 | 5.6.0 |

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

Upgrade craftcms/commerce to a fixed version for your release line: 4.11.0 or 5.6.0.

## Is CVE-2026-32270 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-32270 is a low-severity vulnerability in craftcms commerce, published on 13 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-32270 in the wild and no public exploit code.

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

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-32270/ (Markdown: https://insights.sbomify.com/CVE-2026-32270/index.md)
```

## Sources

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

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