CVE-2025-7289
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 DXF 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 DXF 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-26225.
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 fails to properly validate user-supplied data during DXF file parsing, leading to memory corruption. An attacker can exploit this by tricking a user into opening a malicious DXF file, allowing 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 fileOpen the IrfanView installation directory and look in the 'Plugins' or 'plugins' subfolder for a DLL file related to CAD or DXF handling (commonly named cadimage.dll, CADImage.dll, or similar)Affected if The CADImage plugin DLL file exists in the IrfanView Plugins folder
-
Check the CADImage plugin versionRight-click the CADImage DLL file, select Properties, then go to the Details tab to view the File VersionAffected if The displayed version number is lower than 15.0.0.8 (for example, 15.0.0.7 or earlier)
-
Verify the plugin is loaded by IrfanViewOpen IrfanView, go to Options > Properties/Settings > Plugins, and check if the CADImage plugin appears in the list and is enabledAffected if The CADImage plugin is listed as enabled in IrfanView's plugin configuration
-
Confirm DXF file handling capabilityTry opening a DXF file in IrfanView or check if DXF file type is associated with IrfanViewAffected if IrfanView can open or preview DXF files using the CADImage plugin
You are affected if the CADImage plugin DLL exists in IrfanView, its file version is below 15.0.0.8, and the plugin is enabled to handle DXF 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
Do not open untrusted DXF files. Obtain and apply any available patches for the CADImage plugin from the vendor. Consider using alternative image viewers or disabling the CADImage plugin until a patch is available.
Cadimage 15.0.0.8 or later
- 1. Obtain Cadimage plugin version 15.0.0.8 or later from the official Cadimage vendor
- 2. Close all running instances of IrfanView
- 3. Uninstall the existing Cadimage plugin or navigate to the IrfanView plugins installation directory
- 4. Install the updated Cadimage plugin version 15.0.0.8 or higher
- 5. Restart IrfanView and confirm the CADImage plugin loads without errors
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-7289 — 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-7289 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