CVE-2025-7260
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 Out-Of-Bounds Write 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 write past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-26129.
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 when parsing DXF files, leading to an out-of-bounds write past the end of an allocated buffer. This allows remote attackers to achieve arbitrary code execution in the context of the current user process through malicious DXF files.
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.
-
Verify CADImage plugin presenceLocate the CADImage plugin files in the IrfanView plugins directory (typically \plugins\ or \plugins\cadimage\ in the IrfanView installation folder)Affected if The CADImage plugin files are found in the IrfanView plugins directory
-
Identify CADImage plugin versionCheck the file properties of the CADImage plugin DLL or check any version information file provided with the pluginAffected if The version information shows a version lower than 15.0.0.8 or no version is displayed
-
Confirm IrfanView uses CADImage for DXF filesCheck IrfanView file type associations or try opening a DXF file to see if CADImage is invoked as the handlerAffected if IrfanView opens DXF files using the CADImage plugin (the plugin is active for DXF file handling)
-
Review recent DXF file openingsExamine recently opened files in IrfanView or check for any suspicious DXF files in the application history if availableAffected if Any DXF files have been opened using IrfanView with the CADImage plugin
A user is affected if the CADImage plugin is installed and its version is below 15.0.0.8, and the user has opened or may open 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
Disable or remove the CADImage plugin until an official vendor patch is available, and instruct users to avoid opening untrusted DXF files from unknown sources.
Cadimage 15.0.0.8
- Obtain the latest Cadimage plugin version 15.0.0.8 or later from the official vendor (IrfanView or CADImage)
- Ensure IrfanView is closed before updating the plugin
- Backup the existing CADImage plugin files (typically cadimage.dll and related files in the IrfanView plugins folder)
- Replace the existing CADImage plugin files with the new version 15.0.0.8 or newer
- Verify the file version of the new cadimage.dll matches 15.0.0.8 or higher
- Restart IrfanView and confirm the CADImage plugin loads correctly
- Test opening a DXF file to confirm the plugin functions properly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7260 — 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-7260 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