# GHSA-2w46-vq8h-98vh: Shopware 6's password recovery link does not expire after email change

> Attackers with access to an old email inbox can reset a customer's password using a stale recovery link after the user changes their email address.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Nov 2025

## What is GHSA-2w46-vq8h-98vh?

GHSA-2w46-vq8h-98vh is a vulnerability in shopware/core, published on 14 Nov 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official 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

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 reset link (from before the email change).
7. The system allows password change using the old link.

### Impact
Reproduced on Stable 6.6.10.7 and trunk.

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

4 open source packages ship an affected version, including shopware/core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `shopware/core` | Packagist | All versions | 6.6.10.9 |
| `shopware/core` | Packagist | All versions | 6.6.10.9 |
| `shopware/core` | Packagist | From 6.7.0.0 | 6.7.4.1 |
| `shopware/core` | Packagist | From 6.7.0.0 | 6.7.4.1 |

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

Upgrade shopware/core to a fixed version for your release line: 6.6.10.9 or 6.7.4.1.

## Is GHSA-2w46-vq8h-98vh being exploited?

There is no known exploitation of GHSA-2w46-vq8h-98vh in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-2w46-vq8h-98vh and fix it if it is affected.

What it is: GHSA-2w46-vq8h-98vh is a vulnerability in shopware/core, published on 14 Nov 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-2w46-vq8h-98vh in the wild and no public exploit code.

Affected packages and fixed versions:
- shopware/core (Packagist): affected all versions; fixed in 6.6.10.9
- shopware/core (Packagist): affected all versions; fixed in 6.6.10.9
- shopware/core (Packagist): affected from 6.7.0.0; fixed in 6.7.4.1
- shopware/core (Packagist): affected from 6.7.0.0; fixed in 6.7.4.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-2w46-vq8h-98vh/ (Markdown: https://insights.sbomify.com/GHSA-2w46-vq8h-98vh/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-2w46-vq8h-98vh

---
From sbomify Insights: https://insights.sbomify.com/GHSA-2w46-vq8h-98vh/
Summaries are generated and may contain mistakes; the official description above is the record.