CVE-2025-7268
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 Read 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 read 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-26182.
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 confidenceAn out-of-bounds read vulnerability exists in the IrfanView CADImage Plugin's DXF file parser due to insufficient validation of user-supplied data. The lack of proper bounds checking during DXF file parsing allows reading past the end of an allocated buffer, which can be leveraged by an attacker to achieve remote 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.
-
Confirm CADImage plugin installationLocate the CADImage plugin component on the system. This may appear as cadimage.dll, CADImage.dll, or similar within an IrfanView plugins directory, or as a standalone Cadimage component. Search for files matching 'cadimage*' or 'cad*image*' across common program directories.Affected if The CADImage plugin component is found on the system
-
Identify the installed Cadimage versionRight-click the identified CADImage file and select Properties, then inspect the Version tab. Alternatively, use a tool like 'strings' or a PE viewer to extract version metadata from the binary file. Note the Product Version or File Version field.Affected if The reported version number is lower than 15.0.0.8 (e.g., 15.0.0.7, 14.x.x.x, or earlier)
-
Verify DXF file handling capabilityCheck if the system has associations or handlers configured for .dxf files that invoke the CADImage plugin or IrfanView. Inspect Windows file type associations, registry entries under HKCR\.dxf, or application logs showing recent DXF file operations.Affected if DXF files are configured to open with IrfanView or the CADImage plugin is used for DXF rendering
-
Review recent DXF file accessExamine system logs, browser download histories, or file access audit logs for any recently opened .dxf files. Check email attachments, downloaded items, or shared network locations where DXF files may have been accessed.Affected if DXF files have been opened on the system using IrfanView or the CADImage plugin
A user is affected if the Cadimage plugin version is found to be lower than 15.0.0.8 AND the plugin is used to process DXF files on the system.
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 untrusted or suspicious DXF files. Do not visit untrusted webpages that may attempt to deliver malicious DXF content. Apply vendor patches for the CADImage plugin when available.
Cadimage plugin version 15.0.0.8 or later
- Navigate to the official IrfanView website and locate the CADImage plugin download section
- Download the CADImage plugin version 15.0.0.8 or later
- Close IrfanView if it is currently running
- Install the updated CADImage plugin by replacing the existing plugin files
- Restart IrfanView to ensure the new plugin is loaded
- Avoid opening untrusted DXF files from unknown or untrusted sources as a precautionary measure
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7268 — 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-7268 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