# CVE-2025-0572: Sante PACS Server Web Portal DCM File Parsing Directory Traversal Arbitrary File Write Vulnerability

> Remote authenticated attackers can write arbitrary files via directory traversal in DCM file parsing, potentially compromising the server.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **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:** 30 Jan 2025
- **Updated:** 10 Feb 2025
- **Also known as:** GHSA-mpwr-28xv-5hw9

## What is CVE-2025-0572?

CVE-2025-0572 is a medium-severity path traversal vulnerability in Sante PACS Server, published on 30 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Sante PACS Server Web Portal DCM File Parsing Directory Traversal Arbitrary File Write Vulnerability. This vulnerability allows remote attackers to create arbitrary files on affected installations of Sante PACS Server. Authentication is required to exploit this vulnerability.

The specific flaw exists within the parsing of DCM files. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to write files in the context of the current user. Was ZDI-CAN-25308.

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

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

It affects 1 product.


Products: Santesoft Sante Pacs Server.

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

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

## Is CVE-2025-0572 being exploited?

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

## Other vulnerabilities in Sante PACS Server

- [CVE-2025-2263](https://insights.sbomify.com/CVE-2025-2263/): Santesoft Sante PACS Server Stack-based Buffer Overflow (critical 9.8)
- [CVE-2023-51637](https://insights.sbomify.com/CVE-2023-51637/): Sante PACS Server PG Patient Query SQL Injection Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2024-1863](https://insights.sbomify.com/CVE-2024-1863/): Sante PACS Server Token Endpoint SQL Injection Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2022-2272](https://insights.sbomify.com/CVE-2022-2272/): SQL injection in PACS Server (critical 9.8)
- [CVE-2025-54156](https://insights.sbomify.com/CVE-2025-54156/): Santesoft Sante PACS Server Cleartext Transmission of Sensitive Information (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0572 is a medium-severity path traversal vulnerability in Sante PACS Server, published on 30 Jan 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-0572 in the wild and no public exploit code.

Affected product: Sante PACS Server. 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-0572/ (Markdown: https://insights.sbomify.com/CVE-2025-0572/index.md)
```

## Sources

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

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