CVE-2025-7302
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-26381.
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 flaw stems from insufficient validation of user-supplied data during DWG parsing, allowing attackers to overwrite memory and 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.
-
Locate the CADImage plugin fileCheck the IrfanView Plugins folder (typically C:\Program Files\IrfanView\Plugins\ or C:\Program Files (x86)\IrfanView\Plugins\) for a DLL related to CADImage, CAD, or DWG support (commonly CADImage.dll or similar).Affected if The CADImage plugin DLL exists in the IrfanView plugins directory.
-
Check the installed version of the CADImage pluginRight-click the CADImage DLL file, select Properties, and view the Version tab to find the Product Version or File Version information.Affected if The version number shown is less than 15.0.0.8 (for example, 15.0.0.7 or earlier), or no version information is displayed.
-
Verify DWG file association or support is activeIn IrfanView, go to Options > Properties/Settings > Plugins to confirm the CADImage plugin is loaded and enabled. Alternatively, attempt to open a DWG file or check File > Open for .dwg file type visibility.Affected if The plugin shows as loaded/enabled in the plugins list or .dwg files are recognized as openable.
-
Identify if untrusted DWG files have been opened recentlyReview recent file access in IrfanView, check the application's recent files list, or inspect the file system for recently opened .dwg files from unknown or external sources.Affected if DWG files from untrusted or unknown sources have been opened with IrfanView.
If the CADImage plugin is installed, shows a version below 15.0.0.8, is enabled in IrfanView, and has been used to open DWG files, the environment is 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.
dbcve · scoped15.0.0.8
Avoid opening DWG files from untrusted sources; update the CADImage plugin to the latest patched version once available; consider using antivirus scanning on untrusted files.
Cadimage version 15.0.0.8 or later
- Identify the currently installed Cadimage plugin version
- Navigate to the official Cadimage website or trusted software distribution channel
- Download Cadimage version 15.0.0.8 or later
- Close IrfanView if it is currently running
- Install the updated Cadimage plugin following the vendor's installation instructions
- Restart IrfanView and verify the plugin loads successfully
- Test DWG file opening functionality to confirm the plugin works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7302 — 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-7302 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