# CVE-2025-24489: INFINITT Healthcare INFINITT PACS Unrestricted Upload of File with Dangerous Type

> Attackers can upload arbitrary files to the PACS system, potentially leading to full system compromise.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA: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:** 21 Aug 2025
- **Updated:** 21 Aug 2025
- **Also known as:** GHSA-59h8-p88c-wm46

## What is CVE-2025-24489?

CVE-2025-24489 is a medium-severity vulnerability in INFINITT PACS System Manager, published on 21 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An attacker could exploit this vulnerability by uploading arbitrary 
files via a specific service, which could lead to system compromise.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2025-24489 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-24489 is a medium-severity vulnerability in INFINITT PACS System Manager, published on 21 Aug 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-24489 in the wild and no public exploit code.

Affected product: INFINITT PACS System Manager. 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-24489/ (Markdown: https://insights.sbomify.com/CVE-2025-24489/index.md)
```

## Sources

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

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