Commerce Stripe security updates, in plain English

Commerce Stripe

5,159 sites report using it · on drupal.org · 1 security update explained here

This module connects an online shop to a payment processing service.

Below is every security update for Commerce Stripe that this site has covered, newest first. Each one says who could exploit it, whether it applies to your site, how urgent it is, and what to tell your developer. If your site uses this module and you are not sure which version, that is the first question to ask whoever looks after it.

Commerce Stripe

Critical · 5,159 sites report using it · 3 security fixes · Week of 28 October 2026

3 security fixes in one update. Commerce Stripe fixed 3 separate security bugs at once: 1 cross site request forgery, 1 cross site scripting, 1 improper verification of cryptographic signature. One update covers all of them. The most serious, SA-CONTRIB-2026-263, is explained here and the full list is at the end of the card.

The module does not include a security token when returning from the payment service. Someone could trick an administrator into clicking a link that marks an order as paid without any money changing hands. They could read or change data they should not have access to.

Who could do thisAnyone visiting the site. No login needed.
Does it apply to youAny site using this module.
Has it been used in attacksNo sign of it.
How urgentDrupal rates this critical. Cyber Essentials expects a fix within 14 days. Do it this week.

Tell your developerUpdate Commerce Stripe to 2.2.3.

For developers: what the fix changed

This release carries 3 security fixes. The summary below is for SA-CONTRIB-2026-263, the most serious of them.

The fix generates a random state token in `StripeConnectConfirmationForm::buildForm` and stores it in the session, appending it to the OAuth return URI. It then validates this token against the session in `StripeConnectController` to prevent CSRF attacks.

Also in this release The release also masks the access token in the UI, enforces webhook signing secret validation, adds cacheability metadata to entity operations, sets a field as internal, and renames a test class.

2.2.2 to 2.2.3 1 commit, 6 files including 1 test.

commerce_stripe.module +8 −3
src/Controller/StripeConnectController.php +32 −4 fix
src/Form/StripeConnectConfirmationForm.php +23 −2 fix
src/Plugin/Commerce/PaymentGateway/StripePaymentElement.php +6 −7
src/Plugin/Commerce/PaymentMethodType/StripeDefault.php +2 −1

Full diff, 2.2.2 to 2.2.3

The comparison is against the release immediately before the fix. If your site is on an older release, more will have changed.

All 3 security bugs this update fixes, worst first. Each link is the drupal.org notice for that one.

Critical · Cross site request forgery · SA-CONTRIB-2026-263
Moderately critical · Cross site scripting · SA-CONTRIB-2026-265
Moderately critical · Improper verification of cryptographic signature · SA-CONTRIB-2026-264

Get in touch

Tell me who you are, what your organisation does, and what you need. That might be a Drupal site that needs looking after, an upgrade to get done before December, or an agency that needs Drupal cover.

If I can help, I'll say so and suggest a call. If I can't, I'll tell you straight away rather than waste your time.

For context: I work mainly with UK membership bodies, charities and research organisations, and with the agencies that look after their websites. Not recruiters.

Or start smaller and connect with me on LinkedIn. That's where I post what I find digging around in charity and grants data, and where the free tools turn up first.

Commerce Stripe

Commerce Stripe

Send me your Drupal site's address.

Get in touch

Links

Reference