# CVE-2025-4596: Information disclosure via IDOR in Asseco AMDX

> Logged-in users can access other users' medical records by manipulating document IDs in GET requests, exposing sensitive health data.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/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:** 8 Jan 2026
- **Updated:** 8 Jan 2026
- **Also known as:** GHSA-xfxj-mh7v-h4rr

## What is CVE-2025-4596?

CVE-2025-4596 is a medium-severity vulnerability in Asseco AMDX, published on 8 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Asseco ADMX system is used for processing medical records. It allows logged in users to access medical files belonging to other users through manipulation of GET arguments containing document IDs.
This issue has been fixed in 6.09.01.62 version of ADMX.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2025-4596 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4596 is a medium-severity vulnerability in Asseco AMDX, published on 8 Jan 2026. 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-4596 in the wild and no public exploit code.

Affected product: Asseco AMDX. 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-4596/ (Markdown: https://insights.sbomify.com/CVE-2025-4596/index.md)
```

## Sources

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

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