# ABP Account Module has an Open Redirect through Improper validation in its register function

Advisory record · `GHSA-vfm5-cr22-jg3m`

- **Identifiers:** `GHSA-vfm5-cr22-jg3m` · `CVE-2025-65581`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html) · [CWE-601](https://cwe.mitre.org/data/definitions/601.html)
- **Tags:** [Open redirect](https://agentprime.io/advisories/tag/open-redirect.md) · [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md)
- **Published:** 16 Dec 2025
- **Updated:** 16 Dec 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 16 Dec 2025, 18:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `Volo.Abp.Account.Web` (NuGet): affected `>=5.1.0, <10.0.0-rc.2`; fixed in `10.0.0-rc.2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Volo.Abp.Account.Web package, versions 5.1.0 up to but not including 10.0.0-rc.2, has an open redirect flaw in its register function. Improper validation of the returnUrl parameter lets an attacker send users to arbitrary external domains. Upgrade to Volo.Abp.Account.Web 10.0.0-rc.2 or later. The source gives few details about how the attack is delivered.

Written 9 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.0028, the 20th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:22 UTC: First seen by agentprime
- 31 Oct 2026, 15:22 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-vfm5-cr22-jg3m)

## Sources

- [GitHub Advisory Database: GHSA-vfm5-cr22-jg3m](https://github.com/advisories/GHSA-vfm5-cr22-jg3m)
- [OSV: GHSA-vfm5-cr22-jg3m](https://osv.dev/vulnerability/GHSA-vfm5-cr22-jg3m)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-65581>
- <https://github.com/abpframework/abp/commit/44a2dc14e933f3ce1ca93f9313d836694ab77d1d>
- <https://github.com/abpframework/abp/commit/a01adc58464d278ca817c4bbb6cbce30f155d0d1>
- <https://github.com/abpframework/abp>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-vfm5-cr22-jg3m>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-vfm5-cr22-jg3m/>. Everything for agents: <https://agentprime.io/llms.txt>.
