- Package
- drupal/commerce_stripe
- Fixed in
- 2.2.3
- Published
- Wed 28 Oct 2026, 16:56 LisbonUpdated Mon 2 Nov 2026, 07:25 Lisbon
In plain words
The module leaves out a CSRF token when redirecting to Stripe Connect to generate an authorisation code. An attacker could trick an administrator into clicking a link that causes an order to be marked as paid without any payment being made.
Am I affected?
Look for drupal/commerce_stripe and its version in composer.lock, then check whether your store uses the Stripe Connect authorisation flow described above. The advisory lists 2.2.3 as fixed but gives no affected version range, so it does not establish which other versions are affected.
What to do
Check which version you have, then update to a fixed release for your branch (2.2.3):
composer show drupal/commerce_stripe | grep versions
composer update drupal/commerce_stripeIf your version constraint in composer.json keeps you below a fixed release, raise it first. Whether your configuration is affected, and the exact version ranges, are in the advisory itself.
The advisory's description
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.