Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Informational severity, published 28 October 2026.
- Which products and versions are affected?
- Drupal Commerce Stripe 2.0.0 to 2.2.2; Packagist:Https://Packages.Drupal.Org/8 Drupal/Commerce Stripe ECOSYSTEM:introduced=2.0.0,fixed=2.2.3.
- Is there a fix for This vulnerability?
- Yes. Packagist:Https://Packages.Drupal.Org/8 Drupal/Commerce Stripe: upgrade to 2.2.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run Drupal Commerce Stripe or Packagist:Https://Packages.Drupal.Org/8 Drupal/Commerce Stripe at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Packagist:Https://Packages.Drupal.Org/8 Drupal/Commerce Stripe: upgrade to 2.2.3 or later
Technical details
A cross-site scripting vulnerability exists in Commerce Stripe versions 2.0.0 through 2.2.2 in the payment gateway configuration component. The vulnerability requires an attacker to possess administrator permissions to configure payment gateways and to compromise an external service used in conjunction with Stripe Connect. The fix is available in version 2.2.3.
Affected products
- Drupal Commerce Stripe 2.0.0 to 2.2.2
Timeline
- 2026-10-28: disclosed