# CVE-2023-31861: Path traversal in n/a

> An attacker can exploit a directory traversal vulnerability in ZLMediaKit to read arbitrary files from the server.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 May 2023
- **Updated:** 16 Jan 2025
- **Also known as:** GHSA-qvq6-m5vj-xm45

## What is CVE-2023-31861?

CVE-2023-31861 is a high-severity path traversal vulnerability in n/a, published on 25 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ZLMediaKit 4.0 is vulnerable to Directory Traversal.

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

## Which versions are affected by CVE-2023-31861?

It affects 1 product.


Products: Zlmediakit Zlmediakit.

## How do I fix CVE-2023-31861?

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

## Is CVE-2023-31861 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-35203](https://insights.sbomify.com/CVE-2026-35203/): ZLMediaKit VP9 RTP Parser Out-of-Bounds Read (high 7.5)
- [CVE-2022-37237](https://insights.sbomify.com/CVE-2022-37237/): Denial of service in n/a (high 7.5)
- [CVE-2023-39067](https://insights.sbomify.com/CVE-2023-39067/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-31861 and fix it if it is affected.

What it is: CVE-2023-31861 is a high-severity path traversal vulnerability in n/a, published on 25 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-31861 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-2023-31861/ (Markdown: https://insights.sbomify.com/CVE-2023-31861/index.md)
```

## Sources

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

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