dbcve.org
CadimageApplication · Cadsofttools

CVE-2025-7285

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 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-26221.

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 confidence

The CADImage plugin in IrfanView suffers from a memory corruption vulnerability during DXF file parsing due to insufficient validation of user-supplied data. When a malicious DXF file is opened, the lack of bounds checking or proper input validation leads to memory corruption, allowing an attacker to achieve arbitrary code execution within the context of the current process.

MitigationDisable or remove the CADImage plugin if not required, and instruct users to avoid opening DXF files from untrusted sources until a vendor patch is available. Monitor for IrfanView and plugin updates.

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. Confirm IrfanView installation
    Check if IrfanView is installed by looking for the executable (usually in C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView) or by searching for iview64.exe or i_view64.exe in the system.
    Affected if IrfanView is installed and uses the CADImage plugin.
  2. Locate the CADImage plugin file
    Search for cadimage.dll in the IrfanView plugins folder (typically C:\Program Files\IrfanView\Plugins or C:\Program Files (x86)\IrfanView\Plugins).
    Affected if The cadimage.dll file exists in the plugins folder, indicating the vulnerable plugin is present.
  3. Determine the CADImage plugin version
    Right-click on cadimage.dll, select Properties, then go to the Details tab to view the File Version. Alternatively, use PowerShell: (Get-Item 'C:\Program Files\IrfanView\Plugins\cadimage.dll').VersionInfo.FileVersion
    Affected if The file version is lower than 15.0.0.8, meaning the vulnerability is present.
  4. Verify plugin is registered with IrfanView
    Open IrfanView, go to menu: Options > Properties/Settings > Plug-ins. Check if CADImage plugin is listed as loaded/enabled.
    Affected if The CADImage plugin appears as enabled or loaded in the plugins list.

A user is affected if the CADImage plugin (cadimage.dll) is installed with a version lower than 15.0.0.8 and is enabled in IrfanView, allowing malicious DXF files to trigger the memory corruption vulnerability.

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

Disable or remove the CADImage plugin if not required, and instruct users to avoid opening DXF files from untrusted sources until a vendor patch is available. Monitor for IrfanView and plugin updates.

Recommended fix High confidence

15.0.0.8

  1. Upgrade the Cadimage plugin to version 15.0.0.8 or later to address the memory corruption vulnerability in DXF file parsing
  2. Verify the installed version matches or exceeds 15.0.0.8 after upgrading
  3. Exercise caution when opening DXF files from untrusted sources, even after patching

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7285 — 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-7285 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