dbcve.org
CadimageApplication · Cadsofttools

CVE-2025-7267

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 Out-Of-Bounds Read 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 read past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-26179.

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 lacks proper validation of user-supplied data when parsing DXF files, leading to an out-of-bounds read condition. This occurs because the DXF parser does not validate array bounds before reading data, allowing an attacker to read past the end of an allocated buffer. Successful exploitation can lead to arbitrary code execution in the context of the current process.

MitigationDo not open untrusted DXF files; update to patched version of CADImage plugin when available; consider disabling the plugin if not needed.

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 for CADImage.dll in the IrfanView installation directory, typically under a 'Plugins' or 'Plugins32' subfolder. Common paths include C:\Program Files\IrfanView\Plugins\ or C:\Program Files (x86)\IrfanView\Plugins\.
    Affected if The CADImage.dll file exists in the IrfanView plugins directory.
  2. Check the file version of CADImage.dll
    Right-click the CADImage.dll file, select Properties, then view the Details tab to see the 'File version' or 'Product version' field. Alternatively, use a command like 'powershell (Get-Item "C:\path\to\CADImage.dll").VersionInfo' to retrieve version information.
    Affected if The reported version number is lower than 15.0.0.8 (for example, 15.0.0.7, 14.x.x.x, or earlier).
  3. Confirm IrfanView loads the CADImage plugin
    Open IrfanView, go to Image menu and check if DXF file types are associated with the CADImage plugin, or try to open a DXF file through IrfanView to see if the plugin handles it.
    Affected if IrfanView associates or attempts to use the CADImage plugin for DXF file handling.

You are affected if the CADImage.dll plugin file exists with a version lower than 15.0.0.8 and IrfanView uses it to process DXF 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

Do not open untrusted DXF files; update to patched version of CADImage plugin when available; consider disabling the plugin if not needed.

Recommended fix High confidence

Cadimage 15.0.0.8 or later

  1. 1. Identify all systems with Cadimage (IrfanView CADImage Plugin) installed.
  2. 2. Verify the currently installed version of Cadimage.
  3. 3. Download Cadimage version 15.0.0.8 or later from the official vendor source.
  4. 4. Uninstall the current version of Cadimage.
  5. 5. Install the updated version (15.0.0.8 or newer).
  6. 6. Verify the installation was successful and the version is correct.
  7. 7. Test that DXF files can still be opened and viewed correctly.

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

Fix this in Cadimage Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
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,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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