CVE-2026-32270: Craft Commerce: Unauthenticated information disclosure in `commerce/payments/pay` can leak some customer order data on anonymous payments
Summary
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.
Other sources
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.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-32270?
CVE-2026-32270 is classified as a medium severity vulnerability due to the risk of unauthorized information disclosure.
How do I fix CVE-2026-32270?
To fix CVE-2026-32270, upgrade Craft Commerce to version 4.11.0 or later, or to version 5.5.5 or later.
What versions of Craft Commerce are affected by CVE-2026-32270?
CVE-2026-32270 affects Craft Commerce versions 4.0.0 through 4.10.2 and 5.0.0 through 5.5.4.
What type of information is disclosed in CVE-2026-32270?
CVE-2026-32270 can leak customer order data through the payments action on anonymous payments.
Is user authentication required to exploit CVE-2026-32270?
No, CVE-2026-32270 can be exploited without user authentication.