dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-4596

MEDIUM · 5.3 CVSS v4.0 Published 2026-01-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an Insecure Direct Object Reference (IDOR) vulnerability in the Asseco ADMX medical records system. Authenticated users can view medical files belonging to other users by manipulating document IDs in GET request parameters, indicating missing or inadequate authorization checks on file access operations.

MitigationUpgrade to version 6.09.01.62 or later. Additionally, implement proper authorization validation to ensure users can only access medical documents they are explicitly permitted to view.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Asseco ADMX installation
    Search for ADMX system components or services: check for directories named 'ADMX' or 'admx' in common application paths (C:\Program Files, C:\inetpub, /var/www, /opt), or look for running processes named 'admx' or 'ADMX' in Task Manager (Windows) or ps/ps aux (Linux)
    Affected if The Asseco ADMX medical records system is present in the environment
  2. Locate ADMX version information
    Check common version file locations: look for version.txt, about.ini, or similar in the ADMX installation directory; also check the application's main executable (often named admx.exe or similar) and right-click for Properties > Details to view File Version; alternatively, check the Windows Registry under HKLM\SOFTWARE\Asseco\ADMX or HKLM\SOFTWARE\WOW6432Node\Asseco\ADMX for a Version or InstallPath value
    Affected if The installed version is lower than 6.09.01.62 (the patched version)
  3. Identify document access endpoints
    Review web server configuration (IIS, Apache, Nginx) hosting the ADMX application for URL patterns that handle document or file retrieval, such as paths containing 'document', 'file', 'download', 'view', 'medical' or numeric ID parameters; check web.config (IIS) or .htaccess (Apache) for routing rules related to file access
    Affected if The application exposes HTTP endpoints that accept document IDs as GET parameters for file retrieval
  4. Verify authorization on document access
    As an authenticated user with standard access, attempt to access a medical document by directly modifying the document ID parameter in a known file retrieval URL (e.g., changing ?id=123 to ?id=124); compare the response: if the system returns a medical file or document that belongs to a different user without returning a 403 Forbidden or authorization error, the IDOR vulnerability is present
    Affected if The system allows retrieval of documents belonging to other users by simply changing the document ID parameter without proper authorization validation

A defender is affected if the Asseco ADMX system is installed and the installed version is lower than 6.09.01.62, AND the document retrieval endpoints do not properly validate that the authenticated user has permission to access the requested medical file.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 6.09.01.62 or later. Additionally, implement proper authorization validation to ensure users can only access medical documents they are explicitly permitted to view.

Recommended fix High confidence

6.09.01.62

  1. Upgrade Asseco ADMX system to version 6.09.01.62 or later to address the IDOR vulnerability
  2. After upgrade, verify that proper authorization checks are enforced when accessing medical files via document IDs in GET arguments

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-4596 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-4596 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data