# DRUPAL-CONTRIB-2026-265: This module enables you to use the Stripe Connect API to quickly configure your Drupal Commerce store to take payments via multiple Stripe APIs.


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 28 Oct 2026

## What is DRUPAL-CONTRIB-2026-265?

DRUPAL-CONTRIB-2026-265 is a vulnerability in drupal/commerce_stripe, published on 28 Oct 2026. 

### Official 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.

Under certain rare circumstances, the module may expose a cross-site scripting vulnerability.

This vulnerability is mitigated by the fact that an attacker must have administrator permissions to configure payment gateways and use the Stripe Connect in conjunction with the compromise of an external service.

## Which versions are affected by DRUPAL-CONTRIB-2026-265?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/commerce_stripe` | Packagist:https://packages.drupal.org/8 | From 2.0.0 | 2.2.3 |

## How do I fix DRUPAL-CONTRIB-2026-265?

Upgrade to a fixed version.

## Is DRUPAL-CONTRIB-2026-265 being exploited?

There is no known exploitation of DRUPAL-CONTRIB-2026-265 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for DRUPAL-CONTRIB-2026-265 and fix it if it is affected.

What it is: DRUPAL-CONTRIB-2026-265 is a vulnerability in drupal/commerce_stripe, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2026-265 in the wild and no public exploit code.

Affected product: drupal/commerce_stripe. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/DRUPAL-CONTRIB-2026-265/ (Markdown: https://insights.sbomify.com/DRUPAL-CONTRIB-2026-265/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2026-265

---
From sbomify Insights: https://insights.sbomify.com/DRUPAL-CONTRIB-2026-265/
Summaries are generated and may contain mistakes; the official description above is the record.