CVE-2025-7269
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-26188.
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 confidenceIrfanView CADImage Plugin fails to properly validate user-supplied data when parsing DXF files, leading to an out-of-bounds read vulnerability. This memory access error can be leveraged by attackers to execute arbitrary code in the context of the current user process via a specially crafted malicious DXF file.
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 is installed in IrfanViewOpen IrfanView, go to menu Image > CADImage (or check the Plugins menu for CADImage entry). Alternatively, locate the CADImage plugin file (typically cadimage.dll) in the IrfanView plugins folder.Affected if The CADImage plugin entry appears in the IrfanView menu or the plugin DLL file exists in the plugins directory.
-
Determine the CADImage plugin versionRight-click the CADImage plugin file (cadimage.dll) and select Properties, then view the File Version or Product Version field in the Details tab.Affected if The reported version number is lower than 15.0.0.8.
-
Confirm IrfanView handles DXF files through this pluginOpen IrfanView and attempt to open a DXF file, or check File > Open to see if .dxf file type is associated with IrfanView and loads via the CADImage plugin.Affected if DXF files can be opened directly through IrfanView using the CADImage plugin.
You are affected if the CADImage plugin (cadimage.dll) is present in IrfanView and its version is below 15.0.0.8, and you open DXF files using IrfanView.
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
Apply the vendor patch for the CADImage Plugin when released; until then, avoid opening untrusted DXF files and consider disabling the CADImage plugin in IrfanView.
Cadimage 15.0.0.8 or later
- Verify the current version of Cadimage plugin installed on the system
- Obtain Cadimage version 15.0.0.8 or later from the official vendor (CADImage)
- Uninstall the current version of Cadimage
- Install version 15.0.0.8 or later
- Verify the installed version matches the target fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.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 $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7269 — 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-7269 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