How severe is GHSA-27wp-jvhw-v4xp?

GHSA-27wp-jvhw-v4xp has a CVSS score of 8.3/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-27wp-jvhw-v4xp?

GHSA-27wp-jvhw-v4xp affects the following packages: shopware/core (Packagist), shopware/platform (Packagist), shopware/platform (Packagist), shopware/core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-27wp-jvhw-v4xp?

Update shopware/core to 6.5.8.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-27wp-jvhw-v4xp is resolved across your whole dependency graph.

How do I detect GHSA-27wp-jvhw-v4xp in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for shopware/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-27wp-jvhw-v4xp if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is GHSA-27wp-jvhw-v4xp actively exploited in the wild?

No public exploit code has been indexed for GHSA-27wp-jvhw-v4xp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-27wp-jvhw-v4xp?

GHSA-27wp-jvhw-v4xp has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 59th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-27wp-jvhw-v4xp?

GHSA-27wp-jvhw-v4xp is classified as CWE-1336 (CWE-1336), Code Injection (CWE-94). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-27wp-jvhw-v4xp published, and has it been updated?

GHSA-27wp-jvhw-v4xp was published on August 8, 2024 and was last updated on August 12, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

HIGH severity

Shopware vulnerable to Server Side Template Injection in Twig using deprecation silence tagGHSA-27wp-jvhw-v4xp

HIGHFix: shopware/core@a784aa1

GHSA-27wp-jvhw-v4xp is a high-severity (CVSS 8.3) CWE-1336 vulnerability in shopware/core. A fix is available for shopware/core — see the affected versions and patch details below.

Also known asCVE-2024-42355

Published

Aug 8, 2024

Updated

Aug 12, 2024

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Oct 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-27wp-jvhw-v4xp.

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs59th percentile — riskier than 59% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

🐘shopware/core🐘shopware/platform🐘shopware/platform🐘shopware/core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Shopware has a new Twig Tag sw_silent_feature_call which silences deprecation messages while triggered in this tag. It accepts as parameter a string the feature flag name to silence, but this parameter is not escaped properly and allows execution of code.

Patches

Update to Shopware 6.6.5.1 or 6.5.8.13

Workarounds

For older versions of 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.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`shopware/core`	all versions	6.5.8.13`composer require shopware/core:^6.5.8.13`
🐘Packagist	`shopware/platform`	all versions	6.5.8.13`composer require shopware/platform:^6.5.8.13`
🐘Packagist	`shopware/platform`	≥ 6.6.0.0&&< 6.6.5.1	6.6.5.1`composer require shopware/platform:^6.6.5.1`
🐘Packagist	`shopware/core`	≥ 6.6.0.0&&< 6.6.5.1	6.6.5.1`composer require shopware/core:^6.6.5.1`

Affected Products

1 product · 2 configurations

Application

shopwareshopware

≥ 6.6.0.0 && < 6.6.5.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for shopware/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update shopware/core to 6.5.8.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-27wp-jvhw-v4xp is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

### Impact Shopware has a new Twig Tag `sw_silent_feature_call` which silences deprecation messages while triggered in this tag. It accepts as parameter a string the feature flag name to silence, but this parameter is not escaped properly and allows execution of code. ### Patches Update to Shopware 6.6.5.1 or 6.5.8.13 ### Workarounds For older versions of 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.