CVE-2025-7314
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-26400.
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 parsing logic. The flaw stems from insufficient validation of user-supplied data during DWG file processing, which can lead to controlled memory corruption and allow an attacker to execute arbitrary code within the context of the running 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 the IrfanView installation directory for a DLL related to CADImage or DWG handling (typically in a 'Plugins' subfolder). Common names include CADImage.dll or similar. Use: dir /s /b "C:\Program Files\IrfanView\*CAD*" or locate it manually in the Plugins folder.Affected if The CADImage plugin DLL exists in the IrfanView plugins directory.
-
Determine the installed CADImage plugin versionRight-click the located CADImage DLL file, select Properties, then view the Details tab to find the File Version. Alternatively, use PowerShell: (Get-Item "path\to\CADImage.dll").VersionInfo.FileVersion.Affected if The displayed version is lower than 15.0.0.8 (for example, 15.0.0.7 or earlier).
-
Verify the plugin loads in IrfanViewOpen IrfanView, go to menu: Image > Properties, or check Help > About Plugins. Look for CADImage or DWG in the loaded plugins list. You can also open a DWG file to see if IrfanView attempts to process it.Affected if CADImage plugin appears in the loaded plugins list and IrfanView can open DWG files.
-
Confirm DWG file associations are activeCheck if .dwg file associations point to IrfanView, or if IrfanView is configured to handle DWG files through the CADImage plugin. Attempt to open a DWG file with IrfanView or check IrfanView's file open dialog for DWG support.Affected if IrfanView is configured to open DWG files using the CADImage plugin.
You are affected if the CADImage plugin DLL is present in IrfanView, loads successfully, and its version is lower than 15.0.0.8.
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
Update the IrfanView CADImage plugin to the latest patched version when available. Until then, avoid opening untrusted DWG files and disable the CADImage plugin if not required.
Cadimage version 15.0.0.8 or later
- 1. Identify all systems with Cadimage plugin versions prior to 15.0.0.8 installed.
- 2. Verify that the IrfanView CADImage plugin is installed and note its current version.
- 3. Obtain the fixed Cadimage version 15.0.0.8 or later from the official vendor (Cadimage/Logic or IrfanView distribution channels).
- 4. Uninstall the vulnerable Cadimage plugin version from affected systems.
- 5. Install the updated Cadimage version 15.0.0.8 or newer.
- 6. Verify the installed version matches or exceeds 15.0.0.8.
- 7. Test DWG file parsing functionality to ensure the update does not break legitimate workflows.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7314 — 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-7314 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