CVE-2025-7304
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-26385.
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 in IrfanView suffers from a memory corruption vulnerability during DWG file parsing due to insufficient validation of user-supplied data. An attacker can craft a malicious DWG file that, when opened by a victim, triggers improper memory operations leading to 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 the CADImage plugin fileSearch for CADImage DLL files in the IrfanView plugins directory (typically C:\Program Files\IrfanView\Plugins\ or C:\Program Files (x86)\IrfanView\Plugins\) and note the full path of any CADImage-related DLL foundAffected if A CADImage DLL file exists in the IrfanView plugins folder and its version is below 15.0.0.8
-
Check 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.FileVersion (adjust path as needed)Affected if The displayed File Version is lower than 15.0.0.8 (e.g., 15.0.0.7, 14.x.x.x, etc.)
-
Verify plugin is loaded by IrfanViewOpen IrfanView, go to Options > Properties/Settings > Plugins. Look for the CADImage plugin entry in the list of loaded pluginsAffected if The CADImage plugin appears as Enabled or Loaded in the plugins list
-
Confirm DWG file type handling is activeIn IrfanView, go to Options > File Types or check File > Open to see if .dwg files are listed as supported. Also check if double-clicking a DWG file opens it in IrfanView by defaultAffected if DWG files are listed as supported file types or open automatically in IrfanView, indicating the CADImage plugin is actively handling DWG parsing
-
Check for multiple plugin instancesSearch the entire plugins directory for any additional CADImage DLL files or subdirectories containing the plugin, as older or alternate versions may be presentAffected if Multiple CADImage DLL files exist with different versions, and any version is below 15.0.0.8
You are affected if the CADImage plugin DLL exists in IrfanView and its version is below 15.0.0.8, with DWG file handling enabled.
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
Users should avoid opening untrusted DWG files and disable or remove the CADImage plugin if not required. Monitor for IrfanView and plugin updates from the vendor.
Cadimage version 15.0.0.8 or later
- Identify all systems with Cadimage plugin installed for IrfanView
- Verify current version of Cadimage plugin (check plugin version in IrfanView or file version properties)
- Download Cadimage version 15.0.0.8 or later from the official vendor
- Upgrade Cadimage plugin to version 15.0.0.8 or later
- Verify the update was successful by checking the version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.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 $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7304 — 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-7304 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