# CVE-2025-65897: File upload in n/a

> Authenticated users can upload arbitrary files to overwrite system files, leading to remote code execution or privilege escalation in zdh_web.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Dec 2025
- **Updated:** 5 Dec 2025
- **Also known as:** GHSA-j63w-3qvx-6842

## What is CVE-2025-65897?

CVE-2025-65897 is a high-severity vulnerability in n/a, published on 5 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

zdh_web is a data collection, processing, monitoring, scheduling, and management platform. In zdh_web thru 5.6.17, insufficient validation of file upload paths in the application allows an authenticated user to write arbitrary files to the server file system, potentially overwriting existing files and leading to privilege escalation or remote code execution.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Zhaoyachao Zdh Web.

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

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

## Is CVE-2025-65897 being exploited?

There is no known exploitation of CVE-2025-65897 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65897 is a high-severity vulnerability in n/a, published on 5 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-65897 in the wild and no public exploit code.

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

## Sources

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

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