dbcve.org
Dicom Viewer ProApplication · Santesoft

CVE-2025-5481

HIGH · 7.8 CVSS v3.0 Published 2025-06-06
Fix available
A fix is available. Upgrade to 14.2.0 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
Sante DICOM Viewer Pro DCM File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Sante DICOM Viewer Pro. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of DCM files. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of an allocated object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-26168.

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 a memory corruption vulnerability in Sante DICOM Viewer Pro's DCM file parser. The application fails to properly validate user-supplied data during DICOM file parsing, allowing an out-of-bounds write past the end of an allocated buffer. An attacker can exploit this by tricking a user into opening a specially crafted malicious DCM file, achieving arbitrary code execution in the context of the current process.

MitigationApply vendor patches when available. Until then, exercise extreme caution with DCM files from untrusted sources and consider running the viewer in an isolated environment to limit impact of potential exploitation.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Dicom Viewer ProApplication
Affected:< 14.2.0

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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. Verify Sante DICOM Viewer Pro is installed
    Check for the application in standard installation directories (typically C:\Program Files\Santesoft\DICOM Viewer Pro) or look in Windows Add/Remove Programs
    Affected if The application is present on the system
  2. Identify installed version number
    Locate the executable (dicomviewer.exe) and check its version property, or look in the application's About/Help section
    Affected if Version cannot be determined or is lower than 14.2.0
  3. Compare version against affected range
    Compare your installed version to the affected range (< 14.2.0)
    Affected if Installed version is below 14.2.0 - the vulnerability is present
  4. Confirm DCM file handling capability
    Verify the application can open and parse DCM files (its primary function)
    Affected if DCM file parsing is available - the vulnerable code path can be triggered

If Sante DICOM Viewer Pro is installed with a version lower than 14.2.0, the environment is affected by this vulnerability when processing DCM files.

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
Upgrade available Upgrade to 14.2.0 or later
Fixed in 14.2.0
Interim mitigation

Apply vendor patches when available. Until then, exercise extreme caution with DCM files from untrusted sources and consider running the viewer in an isolated environment to limit impact of potential exploitation.

Recommended fix High confidence

Sante DICOM Viewer Pro 14.2.0 or later

  1. Identify the current installed version of Sante DICOM Viewer Pro
  2. Navigate to the official Sante DICOM Viewer Pro vendor website or trusted download portal
  3. Download version 14.2.0 or later of Sante DICOM Viewer Pro
  4. Close any running instances of Sante DICOM Viewer Pro
  5. Install the downloaded version 14.2.0 or later over the existing installation
  6. Restart the application and verify the version number reflects the upgrade
  7. Avoid opening untrusted or unknown DCM files from unverified sources as a supplementary security measure

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

Fix this in Dicom Viewer Pro Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5481 — 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-5481 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