- Package
- drupal/commerce_stripe
- Fixed in
- 1.4.0, 2.2.3
- Published
- Wed 28 Oct 2026, 16:56 Lisbon
In plain words
The module may process inappropriate webhook events because it does not sufficiently verify their cryptographic signatures when the webhook signing secret is not properly configured. This concerns payment gateway plugins that use webhooks, not every gateway plugin in the module.
Am I affected?
Find drupal/commerce_stripe and its version in composer.lock. The advisory lists 1.4.0 and 2.2.3 as fixed but gives no affected version range. Check whether your payment gateway plugin uses webhooks and whether its payment gateway settings contain a value for the webhook signing secret.
What to do
Check which version you have, then update to a fixed release for your branch (1.4.0, 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.
If you cannot update yet
Set a value for the webhook signing secret in the payment gateway settings. The advisory states that any value prevents inappropriate processing.
The advisory's description
This module enables you to take payments via multiple Stripe APIs.
The module doesn't sufficiently verify the cryptographic signature of a webhook event when a signing secret has not been properly configured in the payment gateway settings.
This vulnerability is mitigated by the fact that not all payment gateway plugins in the module utilize webhooks. Furthermore, any payment gateway configuration with any value for its webhook signing secret will prevent inappropriate processing.