How severe is GHSA-2w46-vq8h-98vh?

GHSA-2w46-vq8h-98vh has a CVSS score of 5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-2w46-vq8h-98vh?

GHSA-2w46-vq8h-98vh affects the following packages: shopware/core (Packagist), shopware/core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-2w46-vq8h-98vh?

Update shopware/core to 6.6.10.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2w46-vq8h-98vh is resolved across your whole dependency graph.

How do I detect GHSA-2w46-vq8h-98vh in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for shopware/core. 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-2w46-vq8h-98vh 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-2w46-vq8h-98vh?

O3 pinpoints whether GHSA-2w46-vq8h-98vh 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-2w46-vq8h-98vh actively exploited in the wild?

No public exploit code has been indexed for GHSA-2w46-vq8h-98vh 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-2w46-vq8h-98vh published, and has it been updated?

GHSA-2w46-vq8h-98vh was published on November 14, 2025 and was last updated on November 14, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-2w46-vq8h-98vh

MEDIUM

Shopware 6's password recovery link does not expire after email change

Published

Nov 14, 2025

Updated

Nov 14, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

🐘shopware/core🐘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

Summary

When a customer changes their email address after requesting a password reset, the old password reset link (tied to the previous email) remains valid. An attacker with access to the old email inbox is potentially able to reset the customer’s password even after the user changes their email address.

PoC

Log in to a Shopware account.
Request a password reset for your current email address.
Copy the password reset link but do not open it.
Log back into your account.n
Navigate to Account Settings → Email and change your email address.
Use the previously copied reset link (from before the email change).
The system allows password change using the old link.

Impact

Reproduced on Stable 6.6.10.7 and trunk.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`shopware/core`	all versions	6.6.10.9
🐘Packagist	`shopware/core`	≥ 6.7.0.0&&< 6.7.4.1	6.7.4.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/core. 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/core to 6.6.10.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2w46-vq8h-98vh 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-2w46-vq8h-98vh 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-2w46-vq8h-98vh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary When a customer changes their email address after requesting a password reset, the old password reset link (tied to the previous email) remains valid. An attacker with access to the old email inbox is potentially able to reset the customer’s password even after the user changes their email address. ### PoC 1. Log in to a Shopware account. 2. Request a password reset for your current email address. 3. Copy the password reset link but do not open it. 4. Log back into your account.n 5. Navigate to Account Settings → Email and change your email address. 6. Use the previously copied r

O3 Security · Impact-Aware SCA

Is GHSA-2w46-vq8h-98vh in your dependencies?

O3 detects GHSA-2w46-vq8h-98vh 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