CVE-2025-65581VulnerabilityPublished 16 Dec 2025

CVE-2025-65581: abp · n/a

Affects abpSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubabpframework/abp`pkg:github/abpframework/abp`Other threats	Affected–	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, organizations should implement strict validation and sanitization of the returnUrl parameter to ensure it only allows redirection to trusted internal URLs. This can be achieved by maintaining a whitelist of allowed domains or paths and rejecting or ignoring any redirect requests to external or untrusted domains. If patch updates become available from Volosoft, organizations should prioritize applying them promptly. In the absence of official patches, developers should consider overriding or customizing the registration function to enforce secure redirect logic. Additionally, organizations should educate users about the risks of clicking on suspicious links, especially those that involve redirects, and implement web filtering solutions to block known malicious domains. Monitoring web application logs for unusual redirect patterns can also help detect exploitation attempts early. Finally, integrating Content Security Policy (CSP) headers and other web security best practices can reduce the attack surface.

Description

CVE-2025-65581 is an open redirect vulnerability in the Account module of the Volosoft ABP Framework versions 5.1.0 up to but not including 10.0.0-rc.2. The vulnerability arises from improper validation of the returnUrl parameter in the user registration function, allowing attackers to redirect users to arbitrary external domains without authorization. This flaw does not impact confidentiality or integrity directly but can be exploited to facilitate phishing or social engineering attacks by redirecting users to malicious websites. The vulnerability has a CVSS score of 5.3 (medium severity), indicating moderate risk with no authentication or user interaction required.

Impact

For European organizations, the primary impact of this vulnerability lies in the potential facilitation of phishing and social engineering attacks. By exploiting the open redirect, attackers can craft URLs that appear to originate from trusted corporate domains but redirect users to malicious websites designed to steal credentials or deliver malware. This can undermine user trust, lead to credential compromise, and potentially facilitate further attacks such as account takeover or lateral movement within networks. Although the vulnerability does not directly compromise system confidentiality or integrity, the indirect consequences can be significant. Organizations in sectors with high user interaction, such as financial services, e-commerce, and public services, are particularly at risk. Additionally, the availability impact is low but could be leveraged in denial-of-service scenarios if combined with other vulnerabilities. Given the widespread use of the ABP Framework in enterprise applications, the risk is amplified in countries with strong software development ecosystems and digital transformation initiatives.

CWE-601URL Redirection to Untrusted Site ('Open Redirect') (opens in a new tab)
Base weaknessLikelihood of exploit: LowOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
Use an intermediate disclaimer page that provides the user with a clear warning that they are leaving the current site. Implement a long timeout before the redirect occurs, or force the user to click on the link. Be careful to avoid XSS problems (CWE-79) when generating the disclaimer page.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
OWASP Cheat Sheets
Mass Assignment (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V5.1.5 (opens in a new tab)
Attack patterns
Cross-Site Flashing (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Dec 2025, 19:34 UTC

WeaknessesCWE-601

Technical details

References

Community reviews

Related threats