CVE-2026-32270

CVE-2026-32270 is a low-severity missing authorization vulnerability in craftcms/commerce (composer), affecting versions >= 5.0.0, <= 5.5.4. It is fixed in 5.6.0, 4.11.0.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Craft Commerce has an unauthenticated information disclosure that can leak some customer order data on anonymous payments

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.

Details

I manually audited frontend payment flows and found that actionPay() retrieves orders by number before authorization is fully enforced.

Code path:

  1. Load order by number.
  2. Evaluate whether payment is authorized for completed orders (number + matching email).
  3. If unauthorized, return failure.
  4. Failure response still includes cartArray($order), which serializes sensitive order data.

Why is this a vulnerability?

  • Authorization logic says the requester is not allowed to pay for a completed order without an email.
  • But the response still returns the same completed order’s contents.

Impact

Type: Information Disclosure / Broken Access Control

Who is impacted:

  • Any Commerce deployment where completed order numbers can be obtained or leaked.

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

Affected versions

craftcms/commerce (>= 5.0.0, <= 5.5.4) craftcms/commerce (>= 4.0.0, <= 4.10.2)

Security releases

craftcms/commerce → 5.6.0 (composer) craftcms/commerce → 4.11.0 (composer)

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

Upgrade the following packages to resolve this vulnerability:

craftcms/commerce to 5.6.0 or later; craftcms/commerce to 4.11.0 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2026-32270? CVE-2026-32270 is a low-severity missing authorization vulnerability in craftcms/commerce (composer), affecting versions >= 5.0.0, <= 5.5.4. It is fixed in 5.6.0, 4.11.0. The application does not perform an authorization check before performing a sensitive operation.
  2. Which versions of craftcms/commerce are affected by CVE-2026-32270? craftcms/commerce (composer) versions >= 5.0.0, <= 5.5.4 is affected.
  3. Is there a fix for CVE-2026-32270? Yes. CVE-2026-32270 is fixed in 5.6.0, 4.11.0. Upgrade to this version or later.
  4. Is CVE-2026-32270 exploitable, and should I be worried? Whether CVE-2026-32270 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
  5. What actually determines whether CVE-2026-32270 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.
  6. How do I fix CVE-2026-32270?
    • Upgrade craftcms/commerce to 5.6.0 or later
    • Upgrade craftcms/commerce to 4.11.0 or later

Other vulnerabilities in craftcms/commerce

Stop the waste.
Protect your environment with Kodem.