CVE-2025-6552VulnerabilityPublished 24 Jun 2025

CVE-2025-6552: java-aodeng Hope-Boot · Open Redirect

Affects java-aodeng Hope-BootSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score

5.3Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Jun 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
Mavenjava-aodeng/Hope-Boot`pkg:maven/java-aodeng/Hope-Boot`Other threats	Affected =1.0.0	Fixed in–

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

AI-suggested

Implement strict validation and sanitization of the redirect_url parameter to allow only whitelisted internal URLs or relative paths. Reject or ignore any URLs that do not conform to the whitelist.

Use a fixed set of redirect destinations encoded as tokens or identifiers instead of accepting arbitrary URLs from user input.

Employ Content Security Policy (CSP) headers to restrict navigation and framing to trusted domains, reducing the risk of malicious redirects.

Educate users and employees about the risks of clicking on unexpected or suspicious links, especially those that appear to redirect through legitimate corporate domains.

Monitor web server logs for unusual redirect_url parameter values and anomalous redirect patterns that may indicate exploitation attempts.

If possible, upgrade or migrate away from Hope-Boot 1.0.0 to a version or alternative framework that addresses this vulnerability once available.

Implement multi-factor authentication (MFA) to reduce the impact of credential theft resulting from phishing attacks leveraging this vulnerability.

Consider deploying web application firewalls (WAFs) with custom rules to detect and block suspicious redirect_url parameter usage.

Description

A vulnerability was found in java-aodeng Hope-Boot 1.0.0. It has been classified as problematic. Affected is the function doLogin of the file /src/main/java/com/hope/controller/WebController.java of the component Login. The manipulation of the argument redirect_url leads to open redirect. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations using the java-aodeng Hope-Boot 1.0.0 framework, this open redirect vulnerability poses a moderate risk primarily related to user trust and phishing. Attackers can craft malicious URLs that appear to originate from legitimate corporate domains, potentially tricking users into divulging credentials or sensitive information. This can lead to credential theft, unauthorized access, or further exploitation through chained attacks. While the vulnerability does not allow direct system compromise, it undermines the integrity of user sessions and can facilitate social engineering attacks. Organizations in sectors with high regulatory scrutiny (e.g., finance, healthcare, government) may face reputational damage and compliance issues if users are compromised via this vector. Additionally, open redirects can be used to bypass web filters and security controls, increasing the attack surface. The lack of vendor response and absence of patches means organizations must proactively implement mitigations. The impact is heightened in environments where Hope-Boot is used for critical authentication workflows or where users are less security-aware.

Summary

CVE-2025-6552 is an open redirect vulnerability identified in version 1.0.0 of the java-aodeng Hope-Boot framework, specifically within the doLogin function of the WebController.java source file. The vulnerability arises due to improper validation or sanitization of the redirect_url parameter, which is used to redirect users after login. An attacker can manipulate this parameter to redirect users to arbitrary external URLs. This type of vulnerability is classified as an open redirect, which can be exploited remotely without requiring authentication. The vulnerability does not directly compromise system confidentiality, integrity, or availability but can be leveraged as part of phishing attacks, social engineering, or to bypass security controls such as same-origin policy or content security policies. The CVSS 4.0 base score is 5.3 (medium severity), reflecting the ease of exploitation (network accessible, no privileges required), the need for user interaction (victim must click a crafted link), and limited impact on confidentiality and integrity. Public exploit details have been disclosed, increasing the risk of exploitation in the wild, although no active exploitation has been reported yet. The vulnerability affects only version 1.0.0 of Hope-Boot, a Java-based web framework, which may be used in enterprise web applications for authentication and session management.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Jun 2025, 02:55 UTC

Technical details

References

Community reviews

Related threats