dbcve.org
CadimageApplication · Cadsofttools

CVE-2025-7320

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

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 contains a memory corruption vulnerability in its DXF file parser. The flaw stems from insufficient validation of user-supplied data during DXF file parsing, leading to out-of-bounds memory access. Successful exploitation allows arbitrary code execution in the context of the current process when a user opens a malicious DXF file.

MitigationUsers should avoid opening untrusted DXF files and should update the CADImage plugin to any available patched version. If the plugin is not required, consider removing or disabling it to reduce attack surface.

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 the IrfanView installation directory for a file related to CADImage (commonly named CadImage.dll, cadimage.dll, or similar) in the plugins subfolder.
    Affected if The CADImage plugin file exists in the IrfanView plugins directory.
  2. Identify the plugin file version
    Right-click the located CADImage plugin file, select Properties, and view the Details tab to find the File Version or Product Version information.
    Affected if The plugin version is lower than 15.0.0.8.
  3. Verify the plugin is registered with IrfanView
    Open IrfanView and go to Image > Information or check the PlugIns menu to confirm the CADImage plugin is loaded and active.
    Affected if The plugin appears in the loaded plugins list.
  4. Confirm DXF file handling is enabled
    Attempt to open or preview a DXF file in IrfanView, or check File > Open with Files of type set to DXF to see if the CADImage plugin handles this file type.
    Affected if DXF files can be opened or previewed through IrfanView using the CADImage plugin.

You are affected if the CADImage plugin is installed, loaded in IrfanView, handles DXF files, and its version is below 15.0.0.8.

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

Users should avoid opening untrusted DXF files and should update the CADImage plugin to any available patched version. If the plugin is not required, consider removing or disabling it to reduce attack surface.

Recommended fix High confidence

Cadimage 15.0.0.8 or later

  1. Identify the installed Cadimage plugin version in IrfanView
  2. Download Cadimage version 15.0.0.8 or the latest stable version from the vendor's official website
  3. Backup any existing Cadimage plugin files and configuration
  4. Close IrfanView completely before installing the update
  5. Install the updated Cadimage plugin (version 15.0.0.8 or later)
  6. Verify the installed version matches the patched release
  7. Restart IrfanView and test with a sample DXF file to confirm proper functionality

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

Fix this in Cadimage Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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