Shopware Storefront Reflected XSS in Storefront Login Page
Published 9 Dec 2025 · Updated 10 Sept 2026
Affected packages
- Affected
- >=6.4.6.0 <6.6.10.10
- Fixed in
- 6.6.10.10
composer require shopware/shopware:^6.6.10.10- Affected
- >=6.4.6.0 <6.6.10.10
- Fixed in
- 6.6.10.10
composer require shopware/storefront:^6.6.10.10- Affected
- >=6.7.0.0 <6.7.5.1
- Fixed in
- 6.7.5.1
composer require shopware/shopware:^6.7.5.1- Affected
- >=6.7.0.0 <6.7.5.1
- Fixed in
- 6.7.5.1
composer require shopware/storefront:^6.7.5.1Details
Impact
By exploiting the XSS vulnerabilities, malicious actors can perform harmful actions in the user's web browser in the session context of the affected user. Some examples of this include, but are not limited to: Obtaining user session tokens. Performing administrative actions (when an administrative user is affected). These vulnerabilities pose a high security risk. Since a sensitive cookie is not configured with the HttpOnly attribute and administrator JWTs are stored in sessionStorage, any successful XSS attack could enable the theft of session cookies and administrative tokens.
Description
A request parameter from the URL of the login page is directly rendered within the Twig template of the Storefront login page without further processing or input validation. This allows direct code injection into the template via the URL parameter. An attacker can create malicious links that could be used in a phishing attack. The parameter waitTime lacks proper input validation.
The attack can be tested with the following URL pattern:
/account/login?loginError=1&waitTime=<a%20href%3D"https%3A%2F%2Fde.wikipedia.org%2Fwiki%2FPhishing">Here<%2Fa>
The same applies to the errorSnippet parameter:
/account/login?loginError=1&errorSnippet=Reset%20your%20password%20%3Ca%20href%3D%22https%3A%2F%2Fde.wikipedia.org%2Fwiki%2FPhishing%22%3Ehere%3C%2Fa%3E.
Is GHSA-6w82-v552-wjw2 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected shopware/shopware, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.