GHSA-vfm5-cr22-jg3m is a medium-severity (CVSS 5.3) Open Redirect vulnerability in Volo.Abp.Account.Web. A fix is available for Volo.Abp.Account.Web — see the affected versions and patch details below.
ABP Account Module has an Open Redirect through Improper validation in its register function
Exploitation Status
No confirmed exploitation observed yet
- 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-vfm5-cr22-jg3m.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-vfm5-cr22-jg3m by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
Volo.Abp.Account.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 open redirect vulnerability exists in the Account module in Volosoft ABP Framework >= 5.1.0 and < 10.0.0-rc.2. Improper validation of the returnUrl parameter in the register function allows an attacker to redirect users to arbitrary external domains.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | Volo.Abp.Account.Web | ≥ 5.1.0&&< 10.0.0-rc.2 | 10.0.0-rc.2dotnet add package Volo.Abp.Account.Web --version 10.0.0-rc.2 |
Affected Products
abpvolosoftDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Volo.Abp.Account.Web, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Volo.Abp.Account.Web to 10.0.0-rc.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vfm5-cr22-jg3m is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.
Frequently Asked Questions
Is GHSA-vfm5-cr22-jg3m in your dependencies?
Find it across NuGet, including transitive dependencies.