# CVE-2025-4838: kanwangzjm Funiture Login LoginServlet.java doPost redirect

> Attackers can redirect users to malicious sites via the login servlet, potentially facilitating phishing attacks against Funiture users.

- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 May 2025
- **Updated:** 19 May 2025
- **Also known as:** GHSA-9853-p5pw-c3vc

## What is CVE-2025-4838?

CVE-2025-4838 is a medium-severity vulnerability in kanwangzjm Funiture, published on 17 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability, which was classified as problematic, was found in kanwangzjm Funiture up to 71ca0fb0658b3d839d9e049ac36429207f05329b. Affected is the function doPost of the file /funiture-master/src/main/java/com/app/mvc/acl/servlet/LoginServlet.java of the component Login. The manipulation of the argument ret leads to open redirect. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available.

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

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


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

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

## Is CVE-2025-4838 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4838 is a medium-severity vulnerability in kanwangzjm Funiture, published on 17 May 2025. An attacker can exploit it over the internet without logging in, 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-4838 exists.

Affected product: kanwangzjm Funiture. 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-4838/ (Markdown: https://insights.sbomify.com/CVE-2025-4838/index.md)
```

## Sources

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

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