GHSA-2hp9-3xfr-r9w2 is a high-severity (CVSS 7.8) CWE-640 vulnerability in Serenity.Net.Core. A fix is available for Serenity.Net.Core — see the affected versions and patch details below.
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-2hp9-3xfr-r9w2.
EPSS Exploitation Probability
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
Serenity.Net.Core.NETSerenity.Net.WebReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
An issue was discovered in Serenity Serene (and StartSharp) before 6.7.0. Password reset links are sent by email. A link contains a token that is used to reset the password. This token remains valid even after the password reset and can be used a second time to change the password of the corresponding user. The token expires only 3 hours after issuance and is sent as a query parameter when resetting. An attacker with access to the browser history can thus use the token again to change the password in order to take over the account.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | Serenity.Net.Core | all versions | 6.7.0dotnet add package Serenity.Net.Core --version 6.7.0 |
| .NETNuGet | Serenity.Net.Web | all versions | 6.7.0dotnet add package Serenity.Net.Web --version 6.7.0 |
Affected Products
sereneserenitystartsharpserenityDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Serenity.Net.Core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Serenity.Net.Core to 6.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2hp9-3xfr-r9w2 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
Is GHSA-2hp9-3xfr-r9w2 in your dependencies?
Find it across NuGet, including transitive dependencies.