CVE-2025-5943
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 · uneditedMicroDicom DICOM Viewer suffers from an out-of-bounds write vulnerability. Remote attackers are able to exploit this issue to potentially execute arbitrary code on affected installations of DICOM Viewer. User interaction is required to exploit the vulnerability in that the user must either visit a malicious website or open a malicious DICOM file locally.
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 confidenceMicroDicom DICOM Viewer contains an out-of-bounds write vulnerability in its DICOM file parsing functionality. Successful exploitation allows remote attackers to potentially execute arbitrary code on affected installations by tricking users into opening malicious DICOM files or visiting malicious websites that deliver crafted DICOM content.
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed MicroDicom Viewer versionOpen MicroDicom Viewer, then navigate to Help > About. Note the version number displayed in the dialog. Alternatively, right-click the MicroDicom executable file in Program Files, select Properties, and check the Details tab for the version info.Affected if The version shown is older than the latest patched version published by MicroDicom.
-
Confirm DICOM file handling is accessibleVerify that you can open DICOM files using the viewer. Try loading a sample DICOM file via File > Open or by dragging a DICOM file into the application window.Affected if The viewer successfully loads DICOM files, meaning the parsing functionality is active and could process malicious content.
-
Check for unexpected file associations or web integrationReview whether MicroDicom is set as the default handler for .dcm files and whether browser plugins or extensions that auto-load DICOM content are enabled. Check browser settings for any MicroDicom-related plugins.Affected if The viewer or its components are configured to automatically process DICOM content from websites or are the default application for DICOM files, increasing exposure to malicious content.
-
Audit recent DICOM file opening activityReview application logs if logging is enabled, or check recent documents/Recent Files list within MicroDicom to see which DICOM files have been opened. Look for any unfamiliar or suspicious files from untrusted sources.Affected if There are records of DICOM files from unknown or untrusted sources being opened.
If the installed version is older than the patched version and the viewer can open DICOM files (whether from local files or web sources), the environment is potentially affected by this vulnerability.
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.
From vendor dataUsers should avoid opening DICOM files from untrusted sources and should only visit trusted websites. Organizations should update to the latest version of MicroDicom Viewer when patches become available.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5943 — 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-5943 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