CVE-2026-118558: Commerce stripe · This module enables you to use the Stripe Connect API to quickly configure your
Affects drupal/commerce_stripeSource GCVE Database
Not known to be exploited : upgrade to 2.2.3 soon.
Data as of 28 Oct 2026, 20:43 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- Patch
- Available – fixed in 2.2.3
Exploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade drupal/commerce_stripe to 2.2.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Packagist https //packages.drupal.org/8drupal/commerce_stripe | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade the Drupal Commerce Stripe module to version 2.2.3 or later, where this vulnerability is fixed. Applying this official patch eliminates the risk of CSRF-based payment bypass attacks.
Description
The Drupal Commerce Stripe module versions 2.0.0 up to but not including 2.2.3 lack a CSRF token in the return URI when redirecting to Stripe Connect for authorization code generation. This vulnerability could allow an attacker to trick an administrator into clicking a malicious link that bypasses Stripe payment for an order, causing the order to be marked as paid without actual payment. A fix is available in version 2.2.3.