# CVE-2025-8737: zlt2000 microservices-platform OauthLogoutSuccessHandler.java onLogoutSuccess redirect

> Attackers can redirect users to malicious sites via the logout handler in zlt2000 microservices-platform, potentially facilitating phishing attacks.

- **Severity:** Medium 5.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Aug 2025
- **Updated:** 8 Aug 2025
- **Also known as:** GHSA-92rf-vjv9-rrjm

## What is CVE-2025-8737?

CVE-2025-8737 is a medium-severity vulnerability in zlt2000 microservices-platform, published on 8 Aug 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2025-8737?


## How do I fix CVE-2025-8737?

No fix has been published for CVE-2025-8737 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-8737 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8737 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-8737 and fix it if it is affected.

What it is: CVE-2025-8737 is a medium-severity vulnerability in zlt2000 microservices-platform, published on 8 Aug 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8737 exists.

Affected product: zlt2000 microservices-platform. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-8737/ (Markdown: https://insights.sbomify.com/CVE-2025-8737/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-8737
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-8737
- OSV: https://osv.dev/vulnerability/CVE-2025-8737

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-8737/
Summaries are generated and may contain mistakes; the official description above is the record.