GHSA-cv25-3gmg-c6m8 is a high-severity (CVSS 8.8) CWE-74 vulnerability in userfrosting/userfrosting. 1 public exploit reference exists, so weaponization risk is real. A fix is available for userfrosting/userfrosting — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-cv25-3gmg-c6m8 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
userfrosting/userfrostingReal-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
In Userfrosting, versions v0.3.1 to v4.6.2 are vulnerable to Host Header Injection. By luring a victim application user to click on a link, an unauthenticated attacker can use the “forgot password” functionality to reset the victim’s password and successfully take over their account.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | userfrosting/userfrosting | ≥ 0.3.1&&< 4.6.3 | 4.6.3composer require userfrosting/userfrosting:^4.6.3 |
Affected Products
userfrostinguserfrostingResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for userfrosting/userfrosting, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update userfrosting/userfrosting to 4.6.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cv25-3gmg-c6m8 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-cv25-3gmg-c6m8 in your dependencies?
Find it across Packagist, including transitive dependencies.