CVE-2025-7312
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 · uneditedIrfanView CADImage Plugin DWG File Parsing Out-Of-Bounds Read Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of IrfanView CADImage Plugin. 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 DWG files. The issue results from the lack of proper validation of user-supplied data, which can result in a read past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-26398.
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 confidenceOut-of-bounds read vulnerability in IrfanView CADImage plugin during DWG file parsing. The lack of proper validation of user-supplied data allows reading past the end of an allocated buffer, which can be leveraged to execute arbitrary code in the context of the current process.
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< 15.0.0.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify CADImage plugin installationLocate the CADImage plugin file (typically CADImage.dll) in the IrfanView plugins directory, commonly found at C:\Program Files\IrfanView\Plugins\ or C:\Program Files (x86)\IrfanView\Plugins\Affected if The CADImage.dll file exists in the IrfanView plugins folder
-
Determine CADImage plugin versionRight-click the CADImage.dll file, select Properties, then navigate to the Details tab to view the File Version. Alternatively, use PowerShell: (Get-Item 'C:\Program Files\IrfanView\Plugins\CADImage.dll').VersionInfo.FileVersionAffected if The displayed version is lower than 15.0.0.8 (e.g., 15.0.0.7, 14.x.x.x, or earlier)
-
Confirm DWG file association or previewOpen IrfanView and attempt to open a DWG file, or check if IrfanView is set as the default viewer for DWG files in Windows. The vulnerability triggers specifically when parsing DWG files.Affected if IrfanView opens or previews DWG files using the CADImage plugin
-
Identify process contextCheck if IrfanView runs with elevated privileges (right-click IrfanView shortcut > Run as Administrator indicator) or if it's a standard user process. The vulnerability executes code in the context of the current process.Affected if IrfanView runs with administrator or higher privileges, as the impact is execution in the current process context
You are affected if the CADImage.dll plugin exists in your IrfanView installation with a version lower than 15.0.0.8 and you open or preview DWG files using IrfanView.
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 · scoped15.0.0.8
Avoid opening untrusted DWG files and ensure IrfanView CADImage plugin is updated to any vendor-provided patch. Consider disabling the CADImage plugin if DWG viewing is not required.
15.0.0.8
- Identify the current version of the CADImage plugin installed with IrfanView
- Navigate to the official IrfanView plugin downloads or Cadimage vendor website
- Download the CADImage plugin version 15.0.0.8 or later
- Close IrfanView if currently running
- Install or update the CADImage plugin to version 15.0.0.8
- Restart IrfanView and verify the plugin version reflects the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7312 — 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-7312 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