Quick answers
- Is CVE-2026-118560 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118560 being exploited in the wild.
- How severe is CVE-2026-118560?
- Informational severity, published 30 October 2026.
- Which products and versions are affected?
- Drupal Commerce Stripe 2.0.0 to 2.2.2.
- Is there a fix for CVE-2026-118560?
- Yes: fixed in Commerce Stripe 2.2.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118560 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-118560?
- Check whether you run 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
- Fixed in: Commerce Stripe 2.2.3
Technical details
The module improperly neutralizes user input during web page generation in the Stripe Connect payment gateway configuration interface, creating a stored XSS vulnerability. Exploitation requires an attacker to have administrator permissions to configure payment gateways and to compromise an external Stripe service. The vulnerability is mitigated by high privilege requirements and the need for external service compromise, which the advisory rates as "Theoretical" exploitability.
Affected products
- Drupal Commerce Stripe 2.0.0 to 2.2.2
Timeline
- 2026-10-28: disclosed
- 2026-10-28: advisory: Drupal Security Advisory SA-CONTRIB-2026-265