Skip to content

← Public intelligence

Packagist package

shopware/storefront

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

5 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.1PackagistPublished

    Shopware Storefront Reflected XSS in Storefront Login Page

    CVE-2025-67648 · GHSA-6w82-v552-wjw2

    Affected
    • Packagist shopware/storefront >= 6.4.6.0, < 6.6.10.10; >= 6.7.0.0, < 6.7.5.1
    Fixed in
    6.7.5.16.6.10.10· Vendor fix available
    Issue
    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…

    Recommended action: Upgrade to 6.7.5.1 or 6.6.10.10 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 7.5PackagistPublished

    Shopware's session is persistent in Cache for 404 pages

    CVE-2024-27917 · GHSA-c2f9-4jmm-v45m

    Affected
    • Packagist shopware/storefront >= 6.5.8.0, < 6.5.8.7
    Fixed in
    6.5.8.7· Vendor fix available
    Issue
    Impact The Symfony Session Handler, pop's the Session Cookie and assign it to the Response. Since Shopware 6.5.8.0 the 404 pages, are cached, to improve the performance of 404 pages. So the cached Response, contains a Session Cookie when the Browser accessing the 404 page, has no cookies yet. The Symfony Session Handler is in use, when no explicit Session configuration has been done. When Redis is in use for Sessions using the PHP Redis extension, this exploiting code is not used. Patches Update to Shopware version 6.5.8.7 Workarounds Using Redis for Sessions, as this does not trigger the exploit code. Example configuration for Redis Consequences As an guest browser session has been cached on a 404 page, every missing image or directly reaching a 404 page will logout the customer or clear his cart.

    Recommended action: Upgrade to 6.5.8.7 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. Medium, CVSS 6.3PackagistPublished

    HTTP caching is marking private HTTP headers as public in Shopware

    CVE-2022-24747 · GHSA-6wrh-279j-6hvw

    Affected
    • Packagist shopware/storefront <= 6.4.8.1
    Fixed in
    6.4.8.2· Vendor fix available
    Issue
    Impact HTTP caching is marking private HTTP headers as public Patches Fixed in recommend updating to the current version 6.4.8.2. You can get the update to 6.4.8.2 regularly via the Auto-Updater or directly via the download overview. https://www.shopware.com/en/download/#shopware-6 Workarounds For older versions of 6.1, 6.2, and 6.3, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.

    Recommended action: Upgrade to 6.4.8.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  4. Medium, CVSS 6.1PackagistPublished

    HTML injection possibility in voucher code form in Shopware

    CVE-2022-24746 · GHSA-952p-fqcp-g8pc

    Affected
    • Packagist shopware/storefront <= 6.4.8.0
    Fixed in
    6.4.8.1· Vendor fix available
    Issue
    Impact HTML injection possibility in voucher code form Patches Patched in 6.4.8.1, maintainers recommend updating to the current version 6.4.8.2. You can get the update to 6.4.8.2 regularly via the Auto-Updater or directly via the download overview. https://www.shopware.com/en/download/#shopware-6 Workarounds For older versions of 6.1, 6.2, and 6.3, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.

    Recommended action: Upgrade to 6.4.8.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  5. Medium, CVSS 4.8PackagistPublished

    Shopware guest session is shared between customers

    CVE-2022-24745 · GHSA-jp6h-mxhx-pgqh

    Affected
    • Packagist shopware/storefront <= 6.4.8.1
    Fixed in
    6.4.8.2· Vendor fix available
    Issue
    Impact Guest sessions are shared between customers when HTTP cache is enabled. Setups with Varnish are not affected by this issue Patches We recommend updating to the current version 6.4.8.2. You can get the update to 6.4.8.2 regularly via the Auto-Updater or directly via the download overview. https://www.shopware.com/en/download/#shopware-6 Workarounds Security Plugin For older versions of 6.1, 6.2, and 6.3, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version. Disable HTTP Cache Disabling HTTP Cache is also a valid workaround

    Recommended action: Upgrade to 6.4.8.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →