HighGHSA-35jp-8cgg-p4wjCVE-2024-42356

Shopware vulnerable to Server Side Template Injection in Twig using Context functions

Published 8 Aug 2024 · Updated 12 Aug 2024

Is your project on an affected shopware/core?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Affected packages

Affected
<6.5.8.13
Fixed in
6.5.8.13
Update to the fixed version for your release line, for example:composer require shopware/core:^6.5.8.13
Affected
<6.5.8.13
Fixed in
6.5.8.13
Update to the fixed version for your release line, for example:composer require shopware/platform:^6.5.8.13
Affected
>=6.6.0.0 <6.6.5.1
Fixed in
6.6.5.1
Update to the fixed version for your release line, for example:composer require shopware/platform:^6.6.5.1
Affected
>=6.6.0.0 <6.6.5.1
Fixed in
6.6.5.1
Update to the fixed version for your release line, for example:composer require shopware/core:^6.6.5.1

Details

Impact

The context variable is injected into almost any Twig Template and allows to access to current language, currency information. The context object allows also to switch for a short time the scope of the Context as a helper with a callable function.

Example call from PHP:

$context->scope(Context::SYSTEM_SCOPE, static function (Context $context) use ($mediaService, $media, &$fileBlob): void {
    $fileBlob = $mediaService->loadFile($media->getId(), $context);
});

This function can be called also from Twig and as the second parameter allows any callable, it's possible to call from Twig any statically callable PHP function/method.

It's not possible as customer to provide any Twig code, the attacker would require access to Administration to exploit it using Mail templates or using App Scripts.

Patches

Update to Shopware 6.6.5.1 or 6.5.8.13

Workarounds

For older versions of 6.1, 6.2, 6.3 and 6.4 corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.

Is GHSA-35jp-8cgg-p4wj 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/core, and gives you the command that fixes it.

More advisories for shopware/core

  • MediumCVE-2026-48013Shopware: SSRF in Media External-Link Endpoint Bypasses IP Validation · 4 Jun 2026
  • MediumCVE-2026-48015Shopware: Stored XSS via SVG file upload — no SVG sanitization · 4 Jun 2026
  • MediumCVE-2026-48016Shopware: Unauthorized Payment Trigger for Foreign Orders via /store-api/handle-payment · 4 Jun 2026
  • MediumCVE-2026-48014Shopware: Admin API ACL Bypass in Order State Transition Endpoints · 4 Jun 2026
  • MediumCVE-2026-48012Shopware SSO referer trust leading to an arbitrary redirect target · 4 Jun 2026
  • LowCVE-2026-48011Shopware: Timing-attack on admin panel allowing enumeration of administrator usernames · 4 Jun 2026
All 65 advisories for shopware/core

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.