dbcve.org
CadimageApplication · Cadsofttools

CVE-2025-7257

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

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

IrfanView CADImage Plugin contains a memory corruption vulnerability in its DXF file parser due to insufficient validation of user-supplied data. A remote attacker can exploit this by tricking a user into opening a malicious DXF file, allowing arbitrary code execution in the context of the current process.

MitigationAvoid opening untrusted DXF files from unknown sources. Monitor vendor updates for the CADImage plugin and apply patches promptly. Consider disabling the CADImage plugin if DXF viewing is 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. Determine if CADImage plugin is installed
    Locate the IrfanView plugins directory (typically \\IrfanView\\Plugins\\) and check for CADImage DLL files (cadimage.dll, CADImage.dll, or similar). Alternatively, open IrfanView, go to Menu > Image > Information to see loaded plugins.
    Affected if The CADImage plugin DLL is present in the IrfanView plugins folder.
  2. Identify the installed CADImage version
    Right-click the CADImage DLL file in the plugins directory, select Properties, then look at the File Version or Product Version field in the Details tab. If using the plugin dialog in IrfanView, check the version listed for CADImage.
    Affected if The version number shown is less than 15.0.0.8.
  3. Confirm DXF file association is enabled
    In IrfanView, check if DXF files can be opened or previewed. Go to Options > Properties/Settings > Plug-ins to see if CADImage is enabled for DXF file types. Also verify if .dxf files open with IrfanView by default.
    Affected if DXF files are associated with IrfanView or CADImage plugin is enabled for DXF file handling.
  4. Verify the vulnerable code path is reachable
    Attempt to open a DXF file in IrfanView using the CADImage plugin. If the plugin loads and processes DXF files without error, the vulnerable parser code path is reachable.
    Affected if The plugin successfully loads and processes DXF files (indicating the vulnerable DXF parser is active).

You are affected if the CADImage plugin is installed with a version lower than 15.0.0.8 and the plugin is enabled to handle DXF files.

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 DXF files from unknown sources. Monitor vendor updates for the CADImage plugin and apply patches promptly. Consider disabling the CADImage plugin if DXF viewing is not required.

Recommended fix High confidence

Cadimage version 15.0.0.8

  1. Upgrade Cadimage plugin to version 15.0.0.8 or later
  2. Verify the upgrade by checking the plugin version in IrfanView's 'About' dialog or plugin information
  3. Ensure all DXF files are from trusted sources after the update

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

Fix this in Cadimage Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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