dbcve.org
CadimageApplication · Cadsofttools

CVE-2025-7241

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

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 CADImage plugin in IrfanView fails to properly validate user-supplied data during DWG file parsing, leading to memory corruption. An attacker can exploit this by tricking a user into opening a specially crafted malicious DWG file, allowing arbitrary code execution in the context of the current process.

MitigationAvoid opening DWG files from untrusted sources; monitor for vendor patches to the CADImage plugin; consider restricting file type associations or using alternative image viewers for DWG files until a patch is available.

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. Check if IrfanView is installed
    Locate IrfanView installation directory, typically in C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView. Verify the i_view64.exe or i_view32.exe executable exists.
    Affected if IrfanView is present on the system
  2. Identify CADImage plugin installation
    Navigate to the IrfanView plugins folder (usually C:\Program Files\IrfanView\Plugins or C:\Program Files (x86)\IrfanView\Plugins). Look for CADImage DLL files such as CADImage.dll, CadImagePlugin.dll, or similar CAD-related plugin files.
    Affected if CADImage plugin DLL is present in the plugins folder
  3. Determine CADImage plugin version
    Right-click the CADImage plugin DLL file, select Properties, then navigate to the Details tab. Note the File Version field. Alternatively, right-click the DLL and select Properties > Digital Signatures to check signing information.
    Affected if The reported version is below 15.0.0.8 or the version cannot be determined (missing version info may indicate unpatched older version)
  4. Check DWG file association with IrfanView
    Open IrfanView, go to Options > Properties/Settings > File associations. Alternatively, right-click any .dwg file in Windows Explorer, select Open with > Choose another app, and see if IrfanView is listed or set as default.
    Affected if IrfanView is associated as the default opener for .dwg files or is available in the Open with list for DWG files

The system is affected if IrfanView with the CADImage plugin is installed and the plugin version is below 15.0.0.8, especially if DWG file associations are enabled.

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 DWG files from untrusted sources; monitor for vendor patches to the CADImage plugin; consider restricting file type associations or using alternative image viewers for DWG files until a patch is available.

Recommended fix Moderate confidence

Cadimage version 15.0.0.8

  1. Obtain the Cadimage plugin version 15.0.0.8 or later from the official vendor
  2. Verify the current installed version of the Cadimage plugin in IrfanView
  3. Upgrade the Cadimage plugin to version 15.0.0.8 or newer
  4. Confirm the upgrade was successful by checking the plugin version

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

Fix this in Cadimage Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,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 $4,896.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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