CVE-2025-5307
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 · uneditedSantesoft Sante DICOM Viewer Pro contains a memory corruption vulnerability. A local attacker could exploit this issue to potentially disclose information and to execute arbitrary code on affected installations of Sante DICOM Viewer Pro.
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 · moderate confidenceSantesoft Sante DICOM Viewer Pro contains a memory corruption vulnerability that can be exploited by a local attacker to potentially disclose sensitive information and execute arbitrary code on affected installations. The high CVSS score reflects the potential for code execution with local access.
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< 14.2.2CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Sante DICOM Viewer Pro is installedCheck for the presence of the Sante DICOM Viewer Pro application in the system. On Windows, look in Program Files or Program Files (x86) for a SanteSoft folder, or search for executable files named 'Sante DICOM Viewer Pro' or similar. The application may also be listed in Add/Remove Programs.Affected if The software is found installed on the system
-
Identify the installed version numberLocate the installed executable (commonly named SanteDicomViewerPro.exe or similar) and right-click to view Properties, then check the Details tab for the File Version or Product Version. Alternatively, open the application and look in the Help menu for an About or Version information option.Affected if The version cannot be determined or is older than 14.2.2
-
Compare version against vulnerability thresholdIf the version was obtained in step 2, compare it numerically to 14.2.2. Any version less than 14.2.2 (such as 14.2.1, 14.1.0, 13.x, or earlier) is considered affected.Affected if The installed version is less than 14.2.2
-
Assess local access exposureSince this is a local attack vector, evaluate who has physical or terminal access to the machine. Check file system permissions on the application directory to ensure only authorized users can modify executable files.Affected if Untrusted users have access to the system where the software is installed
The system is affected if Sante DICOM Viewer Pro is installed with a version number lower than 14.2.2 and untrusted local users can access that system.
Generated from the published advisory. Verify against your own configuration.
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 · scoped14.2.2
Apply vendor patches or updates when available; until then, limit physical and local access to systems running Sante DICOM Viewer Pro and enforce strict file permissions on the application directory.
14.2.2 or later
- Check current installed version of Sante DICOM Viewer Pro (Help > About)
- Backup any important DICOM files and user data
- Download Sante DICOM Viewer Pro version 14.2.2 or later from the official vendor website (www.santesoft.com)
- Run the installer and follow the on-screen prompts to upgrade
- Verify the upgrade was successful by checking Help > About shows version 14.2.2 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5307 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-5307 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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