Shopware: Unauthorized Payment Trigger for Foreign Orders via /store-api/handle-payment

published 2026-06-04 5 mo ago modified 2026-09-10 1 mo ago also GHSA-9v5m-39wh-5chq , EUVD-2026-45239

cvss: 4.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 35%
public exploits: 0; none known

Shopware is an open commerce platform. Prior to 6.6.10.18 and 6.7.10.1, the Store API endpoint /store-api/handle-payment in src/Core/Checkout/Payment/SalesChannel/HandlePaymentMethodRoute.php accepts a user-controlled orderId and forwards it to src/Core/Checkout/Payment/PaymentProcessor.php without verifying order ownership or guest-order authentication, allowing a normal customer or guest context to trigger the payment flow for another user's order while /store-api/order enforces the expected ownership model. This issue is fixed in versions 6.6.10.18 and 6.7.10.1.

Patch / fix

fixed in 2 links 4

packagist shopware/platform 6.6.10.18, 6.7.10.1
packagist shopware/core 6.6.10.18, 6.7.10.1

github.com/shopware/shopware@69dd5b6 commit
github.com/shopware/shopware@df15f2e commit
github.com/shopware/shopware/releases/tag/v6.6.10.18 release
github.com/shopware/shopware/releases/tag/v6.7.10.1 release

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 3 mo ago (2026-07-20)

Exploit prediction

0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	4.3	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
GitHub	3.1	4.3	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
packagist	shopware/platform	>=6.7.0.0, <6.7.10.1 <6.6.10.18	6.7.10.1 6.6.10.18
packagist	shopware/core	>=6.7.0.0, <6.7.10.1 <6.6.10.18	6.7.10.1 6.6.10.18

Affected products

shopware shopware
shopware platform

Classification

Weakness

CWE-639 Authorization Bypass Through User-Controlled Key
CWE-290 Authentication Bypass by Spoofing

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary