CVE-2025-7276
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-26208.
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 DXF file parsing due to insufficient validation of user-supplied data. An attacker can craft a malicious DXF file that, when opened by a victim, triggers the memory corruption and allows arbitrary code execution within 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 or similar CADImage plugin files in the IrfanView program directory (typically C:\Program Files\IrfanView\) or the plugins subfolderAffected if The plugin file exists on the system
-
Determine the CADImage plugin versionRight-click the plugin DLL file, select Properties, then view the Details tab to find the File Version. Alternatively, use a tool like ExifTool or PowerShell (Get-ItemProperty). Compare the version number to 15.0.0.8Affected if The file version is below 15.0.0.8
-
Confirm the plugin is loaded by IrfanViewOpen IrfanView, go to Image menu and check if CAD/DXF file types are listed as supported, or go to Options > Plugins to see if CADImage is listed as loadedAffected if CADImage plugin appears in IrfanView's loaded plugins or DXF files open directly in IrfanView
-
Identify if DXF files have been openedCheck recent file history in IrfanView, or search for recently accessed .dxf files on the system. Also check if the file association for DXF files points to IrfanViewAffected if DXF files have been opened using IrfanView with the CADImage plugin
If the CADImage plugin version is below 15.0.0.8 and the plugin is installed and active in IrfanView, the system is vulnerable when processing untrusted 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
Update the IrfanView CADImage Plugin to the latest patched version, or remove/disable the plugin if not required. Avoid opening untrusted DXF files from unknown sources.
Cadimage version 15.0.0.8 or later
- Identify the current version of Cadimage plugin installed on systems
- Obtain the latest version of Cadimage (version 15.0.0.8 or later) from the official vendor
- Uninstall the current Cadimage plugin version
- Install the fixed version (15.0.0.8 or later) of Cadimage
- Verify the installation was successful by checking the plugin version in IrfanView
- Ensure users only open DXF files from trusted sources to reduce exposure until the patch is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7276 — 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-7276 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