# CVE-2025-65879: Path traversal in n/a

> An authenticated attacker can delete arbitrary files on the server via directory traversal in the goodsimg parameter of the deleteGoods endpoint.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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-479c-6w78-7qfg

## What is CVE-2025-65879?

CVE-2025-65879 is a high-severity path traversal 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

Warehouse Management System 1.2 contains an authenticated arbitrary file deletion vulnerability. The /goods/deleteGoods endpoint accepts a user-controlled goodsimg parameter, which is directly concatenated with the server's UPLOAD_PATH and passed to File.delete() without validation. A remote authenticated attacker can delete arbitrary files on the server by supplying directory traversal payloads.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Yeqifu Warehouse Management System.

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

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

## Is CVE-2025-65879 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-65878](https://insights.sbomify.com/CVE-2025-65878/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65879 is a high-severity path traversal 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65879 exists.

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-65879/ (Markdown: https://insights.sbomify.com/CVE-2025-65879/index.md)
```

## Sources

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

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