# CVE-2025-27721: INFINITT Healthcare INFINITT PACS Exposure of Sensitive System Information to an Unauthorized Control Sphere

> Unauthorized users can access the INFINITT PACS System Manager without proper authorization, leading to exposure of sensitive system information and resources.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2025
- **Updated:** 22 Aug 2025
- **Also known as:** GHSA-89cg-2gw5-2jg7

## What is CVE-2025-27721?

CVE-2025-27721 is a high-severity missing authorization vulnerability in INFINITT PACS System Manager, published on 21 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unauthorized users can access INFINITT PACS System Manager without proper authorization, 
which could lead to unauthorized access to system resources.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

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


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

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

## Is CVE-2025-27721 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-27721 is a high-severity missing authorization vulnerability in INFINITT PACS System Manager, published on 21 Aug 2025. 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-2025-27721 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-27721/ (Markdown: https://insights.sbomify.com/CVE-2025-27721/index.md)
```

## Sources

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

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