shopware/shopware
Affected
- introduced
6.4.6.0, fixed6.6.10.10(ecosystem)
Fixed versions
6.6.10.10
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2025-67648
Shopware Storefront Reflected XSS in Storefront Login Page
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.High Basis: The source's own band: HIGH
6.4.6.0, fixed 6.6.10.10 (ecosystem)6.6.10.10
The export has no generic command for this ecosystem.
6.4.6.0, fixed 6.6.10.10 (ecosystem)6.6.10.10
The export has no generic command for this ecosystem.
6.7.0.0, fixed 6.7.5.1 (ecosystem)6.7.5.1
The export has no generic command for this ecosystem.
6.7.0.0, fixed 6.7.5.1 (ecosystem)6.7.5.1
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0