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

> Attackers can exploit a directory traversal flaw in Datart to write or read arbitrary files via the image upload interface.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A: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:** 24 Sep 2025
- **Updated:** 24 Sep 2025
- **Also known as:** GHSA-mw3f-f3rv-35h3

## What is CVE-2025-56815?

CVE-2025-56815 is a high-severity path traversal vulnerability in n/a, published on 24 Sep 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

Datart 1.0.0-rc.3 is vulnerable to Directory Traversal in the POST /viz/image interface, since the server directly uses MultipartFile.transferTo() to save the uploaded file to a path controllable by the user, and lacks strict verification of the file name.

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

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

It affects 1 product.


Products: Running-Elephant Datart.

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

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

## Is CVE-2025-56815 being exploited?

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

Public exploit code:

- Datart 1.0.0-rc.3 is vulnerable to Directory Traversal in the POST /viz/image interface, since the server directly uses MultipartFile.transferTo() to save the uploaded file to a path controllable by the user, and lacks strict verification of the filename. (github_poc): https://github.com/xiaoxiaoranxxx/CVE-2025-56815

## Other vulnerabilities in n/a

- [CVE-2025-56819](https://insights.sbomify.com/CVE-2025-56819/): Command injection in n/a (critical 9.8)
- [CVE-2025-70828](https://insights.sbomify.com/CVE-2025-70828/): Command injection in n/a (high 8.8)
- [CVE-2025-56816](https://insights.sbomify.com/CVE-2025-56816/): Deserialization in n/a (high 8.8)
- [CVE-2025-70829](https://insights.sbomify.com/CVE-2025-70829/): Information disclosure in n/a (medium 5.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-56815 is a high-severity path traversal vulnerability in n/a, published on 24 Sep 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-56815 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-56815/ (Markdown: https://insights.sbomify.com/CVE-2025-56815/index.md)
```

## Sources

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

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