dbcve.org
CadimageApplication · Cadsofttools

CVE-2025-7235

HIGH · 7.8 CVSS v3.0 Published 2025-07-21
Fix available
A fix is available. Upgrade to 15.0.0.8 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
IrfanView 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-26075.

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 · moderate confidence

The CADImage plugin in IrfanView contains an out-of-bounds write vulnerability in its DXF file parser. The plugin fails to properly validate user-supplied data before writing to memory, allowing an attacker to write past the end of an allocated buffer. Successful exploitation enables arbitrary code execution in the context of the current process when a user opens a malicious DXF file.

MitigationAvoid opening untrusted or unverified DXF files. Apply any vendor patches for the CADImage plugin when released. Consider disabling the CADImage plugin if not required.

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
CadimageApplication
Affected:< 15.0.0.8

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the CADImage plugin file
    Search for 'CadImage' or 'CADImage' DLL files in the IrfanView plugins directory (typically 'C:\Program Files\IrfanView\plugins' or 'C:\Program Files (x86)\IrfanView\plugins')
    Affected if The plugin DLL file is present on the system
  2. Identify the installed version
    Right-click the CadImage DLL file, select Properties, then view the Details tab to find the File Version. Alternatively, use PowerShell: Get-Item 'C:\Path\To\CadImage.dll' | Select-Object Name, VersionInfo
    Affected if The version shown is below 15.0.0.8 or the version cannot be determined (missing version info)
  3. Confirm DXF file association
    Check if DXF files are configured to open with IrfanView using the CADImage plugin. In IrfanView, go to Options > Properties/Settings > Plug-ins to see enabled plugins and their associated file types
    Affected if DXF file type is associated with or handled by the CADImage plugin
  4. Test current process context
    Open Task Manager and note the process name running IrfanView (typically 'i_view64.exe' for 64-bit or 'i_view32.exe' for 32-bit) when viewing image files
    Affected if IrfanView is running with the vulnerable plugin loaded and the user has permissions to open files

A user is affected if the CADImage plugin (version below 15.0.0.8) is installed and configured to handle DXF files in IrfanView, enabling exploitation when opening a malicious DXF file.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 15.0.0.8 or later
Fixed in 15.0.0.8
Interim mitigation

Avoid opening untrusted or unverified DXF files. Apply any vendor patches for the CADImage plugin when released. Consider disabling the CADImage plugin if not required.

Recommended fix Moderate confidence

15.0.0.8

  1. Identify the current version of the Cadimage plugin installed on the system
  2. Navigate to the official Cadimage website or trusted software distribution channel to obtain the latest version
  3. Download Cadimage version 15.0.0.8 or later
  4. Close any running instances of IrfanView that may be using the CADImage plugin
  5. Install the updated Cadimage plugin following the vendor's installation instructions
  6. Verify the installed version matches 15.0.0.8 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cadimage Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7235 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7235 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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