CVE-2025-8737VulnerabilityPublished 8 Aug 2025

CVE-2025-8737: zlt2000 microservices-platform · Open Redirect

Affects zlt2000 microservices-platformSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.1Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/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: Low
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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
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 8 Aug 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-25.

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
zlt2000 microservices-platform	Affected =6.0	Fixed in–

AI-suggested

To mitigate this vulnerability, organizations should implement strict validation and sanitization of the redirect_url parameter to ensure it only allows redirection to trusted internal URLs or domains. Employing a whitelist approach for redirect destinations is recommended. Additionally, updating the zlt2000 microservices-platform to a patched version once available is critical. In the absence of an official patch, organizations can implement web application firewall (WAF) rules to detect and block suspicious redirect_url parameters. User education on phishing risks and monitoring logout-related logs for unusual redirect patterns can also help detect exploitation attempts. Furthermore, implementing Content Security Policy (CSP) headers and secure logout workflows that do not rely on user-supplied redirect parameters can reduce risk. Finally, integrating multi-factor authentication (MFA) and session management best practices can limit the impact of any successful redirection-based attacks.

Description

A vulnerability, which was classified as problematic, was found in zlt2000 microservices-platform up to 6.0.0. This affects the function onLogoutSuccess of the file src/main/java/com/central/oauth/handler/OauthLogoutSuccessHandler.java. The manipulation of the argument redirect_url leads to open redirect. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations using the zlt2000 microservices-platform, this vulnerability could facilitate phishing attacks by redirecting users to malicious websites after logout, potentially leading to credential theft, malware infection, or further social engineering exploits. While the vulnerability itself does not directly compromise system confidentiality or availability, it undermines user trust and can be a stepping stone for more sophisticated attacks. Organizations in sectors with high regulatory scrutiny, such as finance, healthcare, and government, may face reputational damage and compliance issues if user sessions are manipulated. Additionally, since the platform is microservices-based, the vulnerability could affect distributed applications that rely on centralized authentication and logout mechanisms, increasing the attack surface. The medium severity rating suggests that while the immediate technical impact is limited, the indirect consequences through user deception and potential data exposure are significant, especially in environments with sensitive data or critical services.

Summary

CVE-2025-8737 is an open redirect vulnerability identified in the zlt2000 microservices-platform version 6.0.0 and earlier. The vulnerability resides in the onLogoutSuccess function within the OauthLogoutSuccessHandler.java source file. Specifically, the issue arises from improper validation or sanitization of the redirect_url parameter, which an attacker can manipulate to redirect users to arbitrary external URLs after logout. This vulnerability is remotely exploitable without requiring authentication, although it does require user interaction (i.e., the user must follow a crafted link). The CVSS 4.0 base score is 5.1, indicating a medium severity level. The attack vector is network-based with low attack complexity and no privileges required. The impact on confidentiality is none, integrity is low, and availability is none. The vulnerability does not affect system components beyond the redirect behavior, but it can be leveraged in phishing or social engineering attacks to trick users into visiting malicious sites under the guise of a trusted platform. The exploit has been publicly disclosed but no known exploits in the wild have been reported yet. The vulnerability affects the logout success handler, which is a critical part of user session management in the microservices platform, potentially undermining user trust and session security if exploited.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Aug 2025, 20:02 UTC

Technical details

References

Community reviews

Related threats