# CVE-2026-48016: Shopware: Unauthorized Payment Trigger for Foreign Orders via /store-api/handle-payment

> Attackers can trigger payment flows for other users' orders via the Store API due to missing ownership verification, potentially disrupting transactions.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-9v5m-39wh-5chq

## What is CVE-2026-48016?

CVE-2026-48016 is a medium-severity missing authorization vulnerability in shopware platform, published on 17 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-48016?

8 open source packages ship an affected version, including shopware/platform and shopware/core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `shopware/platform` | Packagist | All versions | 6.6.10.18 |
| `shopware/platform` | Packagist | All versions | 6.6.10.18 |
| `shopware/platform` | Packagist | From 6.7.0.0 | 6.7.10.1 |
| `shopware/platform` | Packagist | From 6.7.0.0 | 6.7.10.1 |
| `shopware/core` | Packagist | All versions | 6.6.10.18 |
| `shopware/core` | Packagist | All versions | 6.6.10.18 |
| `shopware/core` | Packagist | From 6.7.0.0 | 6.7.10.1 |
| `shopware/core` | Packagist | From 6.7.0.0 | 6.7.10.1 |

## How do I fix CVE-2026-48016?

Upgrade shopware/platform to a fixed version for your release line: 6.6.10.18 or 6.7.10.1.

## Is CVE-2026-48016 being exploited?

There is no known exploitation of CVE-2026-48016 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48016 and fix it if it is affected.

What it is: CVE-2026-48016 is a medium-severity missing authorization vulnerability in shopware platform, published on 17 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48016 in the wild and no public exploit code.

Affected packages and fixed versions:
- shopware/platform (Packagist): affected all versions; fixed in 6.6.10.18
- shopware/platform (Packagist): affected all versions; fixed in 6.6.10.18
- shopware/platform (Packagist): affected from 6.7.0.0; fixed in 6.7.10.1
- shopware/platform (Packagist): affected from 6.7.0.0; fixed in 6.7.10.1
- shopware/core (Packagist): affected all versions; fixed in 6.6.10.18
- shopware/core (Packagist): affected all versions; fixed in 6.6.10.18
- shopware/core (Packagist): affected from 6.7.0.0; fixed in 6.7.10.1
- shopware/core (Packagist): affected from 6.7.0.0; fixed in 6.7.10.1

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/CVE-2026-48016/ (Markdown: https://insights.sbomify.com/CVE-2026-48016/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48016
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48016
- OSV: https://osv.dev/vulnerability/CVE-2026-48016

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