dbcve.org
CadimageApplication · Cadsofttools

CVE-2025-7299

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

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 vulnerability exists in IrfanView's CADImage plugin during DWG file parsing. The lack of proper validation of user-supplied data in the DWG parser leads to memory corruption, allowing an attacker to achieve arbitrary code execution in the context of the current process by tricking a user into opening a malicious DWG file.

MitigationAvoid opening DWG files from untrusted sources; disable the CADImage plugin if DWG viewing is not required; monitor for plugin updates from IrfanView; scan files with antivirus before opening.

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 is installed
    Check for IrfanView installation directory (typically C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView) and confirm the executable i_view64.exe or i_view32.exe exists
    Affected if IrfanView is installed and the CADImage plugin is present
  2. Locate the CADImage plugin
    Navigate to the IrfanView plugins folder (usually in the installation directory under Plugins or Plugins32) and verify CADImage.dll or CADImage.exe is present
    Affected if The CADImage plugin file exists in the plugins directory
  3. Check CADImage plugin version
    Right-click the CADImage.dll file, select Properties, then view the Details tab to find the File Version; alternatively, use a tool like ExifTool or view version info via command line
    Affected if The plugin version is lower than 15.0.0.8 or the version cannot be determined (indicating an older release)
  4. Confirm DWG file handling is enabled
    Open IrfanView, go to Options > Plugins and verify the CADImage plugin is enabled; also check that file associations for .dwg may be registered with IrfanView
    Affected if The CADImage plugin is enabled and .dwg files can be opened directly through IrfanView

User is affected if IrfanView with the CADImage plugin below version 15.0.0.8 is installed and the plugin is enabled, allowing malicious DWG files to be opened.

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; disable the CADImage plugin if DWG viewing is not required; monitor for plugin updates from IrfanView; scan files with antivirus before opening.

Recommended fix Moderate confidence

Cadimage version 15.0.0.8 or later

  1. Identify the Cadimage plugin version currently installed in IrfanView
  2. Navigate to the official Cadimage website or trusted software distribution source to obtain the latest version
  3. Download Cadimage version 15.0.0.8 or later
  4. Close IrfanView if it is currently running
  5. Install the updated Cadimage plugin following standard installation procedures
  6. Restart IrfanView and verify the plugin version is 15.0.0.8 or higher
  7. Exercise caution when opening DWG files from untrusted sources

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

Fix this in Cadimage Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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