CVE-2025-7311
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 Memory Corruption 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 memory corruption condition. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-26395.
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 confidenceThe CADImage plugin for IrfanView contains a memory corruption vulnerability in its DWG file parser. The root cause is improper validation of user-supplied data during DWG file parsing, leading to memory corruption that can be leveraged for arbitrary code execution 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.
-
Locate CADImage plugin installationSearch for CADImage plugin files in the IrfanView plugins directory (typically \Program Files\IrfanView\Plugins or \Program Files (x86)\IrfanView\Plugins). Look for files named CadImage.dll, CADImage.dll, or similar CAD-related DLLs.Affected if The CADImage plugin 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 a tool like PowerShell: (Get-Item 'C:\Program Files\IrfanView\Plugins\CadImage.dll').VersionInfo.FileVersionAffected if The installed version is below 15.0.0.8
-
Verify plugin is loaded by IrfanViewOpen IrfanView, go to menu Options > Plugins > Plugins/Options. Check if CADImage plugin appears in the list of loaded plugins.Affected if CADImage appears as an active/loaded plugin in IrfanView's plugin list
-
Confirm DWG file handling is enabledAttempt to open a DWG file with IrfanView or check the plugin configuration for DWG file type associations. DWG files must be processed by the CADImage plugin for the vulnerability to be triggered.Affected if IrfanView is configured to open or preview DWG files using the CADImage plugin
A user is affected if the CADImage plugin for IrfanView is installed with a version lower than 15.0.0.8 and is actively handling DWG files.
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 or unverified DWG files until a vendor patch is available. Consider disabling the CADImage plugin if not required, and scan all downloaded files with antimalware solutions.
Cadimage version 15.0.0.8 or later
- Identify the installed Cadimage plugin version used with IrfanView
- Locate and download Cadimage version 15.0.0.8 or later from the official vendor (Cadimage/Logicor or authorized distribution channel)
- Close all instances of IrfanView
- Install the updated Cadimage plugin version 15.0.0.8 or newer
- Restart IrfanView and verify the plugin loads correctly
- Test DWG file opening functionality to confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7311 — 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-7311 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