dbcve.org
CadimageApplication · Cadsofttools

CVE-2025-7318

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 DWG 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 DWG 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-26412.

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 vulnerability exists in IrfanView's CADImage Plugin during DWG file parsing. The flaw results from insufficient validation of user-supplied data, leading to memory corruption. An attacker can exploit this by tricking a user into opening a malicious DWG file, allowing arbitrary code execution in the context of the current process.

MitigationApply the vendor-supplied patch for the CADImage plugin when available; until then, avoid opening untrusted DWG files and 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 installation
    Navigate to the IrfanView plugins folder (typically C:\Program Files\IrfanView\Plugins or C:\Program Files (x86)\IrfanView\Plugins) and search for files with 'cadimage' or 'cad' in the filename, such as CADImage.dll or CadImage.dll.
    Affected if The CADImage plugin DLL file is present in the IrfanView plugins directory.
  2. Identify the CADImage plugin version
    Right-click the CADImage DLL file, select Properties, then go to the Details tab to view the File Version. Alternatively, open IrfanView, go to menu: Image > Information or check the plugin information dialog to see loaded plugin versions.
    Affected if The displayed version number is lower than 15.0.0.8 (for example, 15.0.0.7, 14.x.x.x, or earlier).
  3. Verify the plugin is enabled in IrfanView
    Open IrfanView, go to Options > Properties/Settings > Plugins. Look for the CADImage plugin in the list and confirm it is checked or enabled. Also check if DWG file types are associated with IrfanView in Windows file associations.
    Affected if The CADImage plugin is enabled and listed as an active plugin in IrfanView's plugin configuration.

You are affected if the CADImage plugin (Cadimage.dll) is installed in IrfanView with a version lower than 15.0.0.8 and the plugin is enabled for loading.

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

Apply the vendor-supplied patch for the CADImage plugin when available; until then, avoid opening untrusted DWG files and consider disabling the CADImage plugin if not required.

Recommended fix Moderate confidence

Cadimage 15.0.0.8 or later

  1. Identify the installed Cadimage plugin version in IrfanView
  2. Navigate to the official Cadimage website or authorized distribution channel
  3. Download Cadimage version 15.0.0.8 or the latest stable version
  4. Close IrfanView completely if running
  5. Run the Cadimage installer/upgrade package
  6. Follow the on-screen installation prompts
  7. Restart IrfanView and verify the plugin loads correctly
  8. Test with a safe DWG file to confirm functionality

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

Fix this in Cadimage Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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