CadimageApplication · Cadsofttools

CVE-2025-7305

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

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 lacks proper input validation when parsing DWG (Drawing) files. The vulnerability stems from insufficient validation of user-supplied data during the DWG file parsing process, leading to memory corruption. Successful exploitation allows an attacker to execute arbitrary code in the context of the current process by tricking a user into opening a malicious DWG file.

MitigationUsers should avoid opening untrusted or unverified DWG files until a patch is available from the vendor. Organizations should deploy endpoint detection and monitoring solutions and consider restricting file handling permissions for the affected plugin.

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. Verify IrfanView installation
    Check if IrfanView is installed on the system. Common installation paths: C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView. Look for irfanview.exe
    Affected if IrfanView is present on the system
  2. Locate CADImage plugin
    Check for CADImage plugin files in the IrfanView plugins directory. Typically found at C:\Program Files\IrfanView\Plugins\ or C:\Program Files (x86)\IrfanView\Plugins\. Look for files named CadImage.dll or similar CADImage-related DLLs
    Affected if CADImage plugin DLL exists in the IrfanView plugins folder
  3. Determine CADImage plugin version
    Right-click the CADImage DLL file, select Properties, and check the File Version tab. Alternatively, use PowerShell: (Get-Item 'C:\Program Files\IrfanView\Plugins\CadImage.dll').VersionInfo | Select-Object FileVersion
    Affected if The reported version number is less than 15.0.0.8 (e.g., 15.0.0.7, 14.x.x.x, etc.)
  4. Confirm DWG file association or capability
    Check if the CADImage plugin handles DWG files by opening IrfanView, going to Options > Plugins Settings, or by attempting to open a DWG file through IrfanView to see if CADImage is invoked
    Affected if IrfanView uses the CADImage plugin to render or preview DWG files, enabling the vulnerable code path

The environment is affected if IrfanView with CADImage plugin version below 15.0.0.8 is installed and the plugin is capable of processing DWG 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

Users should avoid opening untrusted or unverified DWG files until a patch is available from the vendor. Organizations should deploy endpoint detection and monitoring solutions and consider restricting file handling permissions for the affected plugin.

Recommended fix High confidence

Cadimage 15.0.0.8 or later

  1. Identify all systems with the Cadimage plugin installed for IrfanView
  2. Obtain Cadimage version 15.0.0.8 or later from the official Cadimage vendor
  3. Uninstall the current Cadimage plugin version
  4. Install the updated Cadimage version 15.0.0.8 or later
  5. Restart IrfanView if it was running during the update
  6. Verify the installed version is 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
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-7305 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