How severe is GHSA-qvc5-cfrr-384v?

No CVSS score has been assigned to GHSA-qvc5-cfrr-384v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qvc5-cfrr-384v?

GHSA-qvc5-cfrr-384v affects the following packages: shopware/platform (Packagist), shopware/core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-qvc5-cfrr-384v?

Update shopware/platform to 6.3.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qvc5-cfrr-384v is resolved across your whole dependency graph.

How do I detect GHSA-qvc5-cfrr-384v in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for shopware/platform. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-qvc5-cfrr-384v if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-qvc5-cfrr-384v?

O3 pinpoints whether GHSA-qvc5-cfrr-384v is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-qvc5-cfrr-384v actively exploited in the wild?

No public exploit code has been indexed for GHSA-qvc5-cfrr-384v 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.

When was GHSA-qvc5-cfrr-384v published, and has it been updated?

GHSA-qvc5-cfrr-384v was published on September 23, 2020 and was last updated on December 2, 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

GHSA-qvc5-cfrr-384v

GHSA-qvc5-cfrr-384v is a remote code execution vulnerability in shopware/platform. O3 Security confirms whether GHSA-qvc5-cfrr-384v is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

RCE in Third Party Library in Shopware

Published

Sep 23, 2020

Updated

Dec 2, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🐘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

RCE in Third Party Library

Patches

We recommend to update to the current version 6.3.1.1. You can get the update to 6.3.1.1 regularly via the Auto-Updater or directly via the download overview.

For older versions you can use the Security Plugin: https://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659

References

https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-09-2020

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`shopware/platform`	all versions	6.3.1.1
🐘Packagist	`shopware/core`	all versions	6.3.1.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for shopware/platform. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update shopware/platform to 6.3.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qvc5-cfrr-384v is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-qvc5-cfrr-384v is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-qvc5-cfrr-384v. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact RCE in Third Party Library ### Patches We recommend to update to the current version 6.3.1.1. You can get the update to 6.3.1.1 regularly via the Auto-Updater or directly via the download overview. For older versions you can use the Security Plugin: https://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659 ### References https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-09-2020

O3 Security · Impact-Aware SCA

Is GHSA-qvc5-cfrr-384v in your dependencies?

O3 detects GHSA-qvc5-cfrr-384v across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works