SA-CONTRIB-2026-263: CSRF
This module enables you to use the Stripe Connect API to quickly configure your Drupal Commerce store to take payments via multiple Stripe APIs. When redirecting to Stripe Connect to generate an authorization code, the module does not incorporate a CSRF token into the return URI. This could allow a an attacker to trick an administrator to click a link that bypasses Stripe payment for an order, meaning that the order would be marked as paid without any actual payment.
Credit
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
composer/drupal/commerce_stripeto a version that resolves this vulnerability.Fixed in 2.2.3
Event History
Frequently Asked Questions
Who is exposed to this issue?
Drupal Commerce stores using the commerce_stripe module and Stripe Connect authorization flow are exposed. The described impact requires an administrator who can be tricked into clicking an attacker-controlled link.
What can an attacker achieve?
An attacker may cause the Stripe Connect authorization return flow to bypass Stripe payment for an order. The affected order could then be marked as paid even though no payment was made.
What is required for exploitation?
The attacker needs to persuade an administrator to click a link. The issue arises because the authorization return URI does not include a CSRF token.