How severe is GHSA-wq3r-jwrq-xg6w?

No CVSS score has been assigned to GHSA-wq3r-jwrq-xg6w yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wq3r-jwrq-xg6w?

GHSA-wq3r-jwrq-xg6w affects the following packages: shopware/platform (Packagist), shopware/core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-wq3r-jwrq-xg6w?

Update shopware/platform to 6.4.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wq3r-jwrq-xg6w is resolved across your whole dependency graph.

How do I detect GHSA-wq3r-jwrq-xg6w in my Packagist dependencies?

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

How do I mitigate GHSA-wq3r-jwrq-xg6w 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.

Is GHSA-wq3r-jwrq-xg6w actively exploited in the wild?

No public exploit code has been indexed for GHSA-wq3r-jwrq-xg6w 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-wq3r-jwrq-xg6w published, and has it been updated?

GHSA-wq3r-jwrq-xg6w was published on June 28, 2021 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

Canceling of orders not related to the logged-in userGHSA-wq3r-jwrq-xg6w

GHSA-wq3r-jwrq-xg6w is a security vulnerability in shopware/platform. A fix is available for shopware/platform — see the affected versions and patch details below.

Published

Jun 28, 2021

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

Canceling of orders not related to the logged-in user

Patches

We recommend updating to the current version 6.4.1.1. You can get the update to 6.4.1.1 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.

https://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`shopware/platform`	all versions	6.4.1.1`composer require shopware/platform:^6.4.1.1`
🐘Packagist	`shopware/core`	all versions	6.4.1.1`composer require shopware/core:^6.4.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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update shopware/platform to 6.4.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wq3r-jwrq-xg6w 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.

Frequently Asked Questions

### Impact Canceling of orders not related to the logged-in user ### Patches We recommend updating to the current version 6.4.1.1. You can get the update to 6.4.1.1 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. https://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659

O3 Security · Impact-Aware SCA

Is GHSA-wq3r-jwrq-xg6w in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

Canceling of orders not related to the logged-in userGHSA-wq3r-jwrq-xg6w

Real-World Exposure

Description

Impact

Patches

Workarounds

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-wq3r-jwrq-xg6w in your dependencies?