CVE-2026-48012
published 2026-07-23CVE-2026-48012: Shopware is an open commerce platform. Versions 6.7.3.0 through 6.7.10.0 have an open redirect in Shopware's public SSO entry point at `GET…
PriorityP425medium4.3CVSS 3.1
AVNACLPRNUIRSUCNILAN
EPSS
0.27%
18.9th percentile
Shopware is an open commerce platform. Versions 6.7.3.0 through 6.7.10.0 have an open redirect in Shopware's public SSO entry point at `GET /api/oauth/sso/auth`. When the endpoint is reached without the expected SSO session state, the application falls back to the request's `Referer` header and uses that value as the redirect destination. In the validated behavior, the server does not restrict that fallback target to same-origin URLs, does not require a relative path, and does not reject dangerous schemes such as `javascript:`. As a result, an unauthenticated request can turn this endpoint into a reusable redirect primitive whose destination is fully controlled by attacker-supplied request metadata. The security problem is not limited to a harmless navigation mismatch. The endpoint sits under `/api/oauth/`, which gives the redirect a trustworthy application-controlled origin and makes it suitable for phishing chains, branded redirect abuse, and cases where client software automatically follows redirects issued by a trusted host. The attached evidence also shows that the response is not only an HTTP `302` with a user-controlled `Location` header. The HTML body contains a matching meta refresh tag and redirect link built from the same attacker-controlled value. In the validated proof, the endpoint redirects to `https://attacker.example/poc` when that URL is supplied through `Referer`, and it also reflects `javascript:alert(1)` into `Location` and the HTML redirect body without any scheme filtering. This report therefore stays conservative and claims an open redirect with arbitrary redirect targets, while noting that the lack of scheme restrictions makes the behavior materially worse than a same-scheme external redirect. Version 6.7.10.1 fixes the issue.
Affected
4 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| shopware | core | >= 6.7.3.0 < 6.7.10.1 | 6.7.10.1 |
| shopware | platform | — | — |
| shopware | platform | >= 6.7.3.0 < 6.7.10.1 | 6.7.10.1 |
| shopware | shopware | — | — |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
Shopware up to 6.7.10.0 SSO Entry Point /api/oauth/sso/auth Referer redirect
vuldb·2026-07-23·CVSS 4.3
CVE-2026-48012 [MEDIUM] Shopware up to 6.7.10.0 SSO Entry Point /api/oauth/sso/auth Referer redirect
A vulnerability was found in Shopware up to 6.7.10.0. It has been rated as problematic. The affected element is an unknown function of the file /api/oauth/sso/auth of the component SSO Entry Point. This manipulation of the argument Referer causes open redirect.
This vulnerability is registered as CVE-2026-48012. Remote exploitation of the attack is possible. No exploit is available.
Upgrading the affected component is advised.
GHSA
Shopware SSO referer trust leading to an arbitrary redirect target
ghsa·2026-06-04
CVE-2026-48012 [MEDIUM] CWE-601 Shopware SSO referer trust leading to an arbitrary redirect target
Shopware SSO referer trust leading to an arbitrary redirect target
## Description
This report describes an open redirect in Shopware's public SSO entry point at `GET /api/oauth/sso/auth`. When the endpoint is reached without the expected SSO session state, the application falls back to the request's `Referer` header and uses that value as the redirect destination. In the validated behavior, the server does not restrict that fallback target to same-origin URLs, does not require a relative path, and does not reject dangerous schemes such as `javascript:`. As a result, an unauthenticated request can turn this endpoint into a reusable redirect primitive whose destination is fully controlled by attacker-supplied request metadata.
The security problem is not limited to a harmless navigation m
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2026-07-23
Published