CVE-2025-7319
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 · uneditedIrfanView CADImage Plugin DWG 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 DWG 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-26413.
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 confidenceThe CADImage Plugin in IrfanView fails to properly validate user-supplied data when parsing DWG files, leading to an out-of-bounds read past the end of an allocated buffer. This memory corruption can be weaponized to achieve remote code execution in the context of the current process. Exploitation requires user interaction—either visiting a malicious webpage or opening a crafted DWG file.
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< 15.0.0.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if IrfanView is installedSearch for IrfanView installation directories on the system, typically under Program Files or Program Files (x86), or check common application data locations.Affected if IrfanView is present and the CADImage plugin is used for handling DWG files.
-
Locate the CADImage pluginFind the CADImage plugin file (commonly named cadimage.dll or similar) within the IrfanView plugins folder structure.Affected if The CADImage plugin file exists in the IrfanView installation.
-
Retrieve the CADImage plugin versionRight-click the plugin file, select Properties, and view the Version tab to obtain the file version information, or use command-line tools to query file metadata.Affected if The plugin version displayed is below 15.0.0.8.
-
Confirm DWG file handling is enabledCheck if DWG file associations or preview functionality are configured in IrfanView, or verify that the CADImage plugin is loaded when opening DWG files.Affected if The plugin processes DWG files and is loaded by IrfanView.
The environment is affected if IrfanView with the CADImage plugin (cadimage.dll) version below 15.0.0.8 is installed and configured to handle DWG files.
Generated from the published advisory. Verify against your own configuration.
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 · scoped15.0.0.8
Avoid opening untrusted or unverified DWG files until a patch is available from IrfanView. Keep antivirus software updated and monitor for security advisories from the vendor.
Cadimage 15.0.0.8 or later
- Identify the currently installed Cadimage version through the application's 'About' or 'Help' menu
- Download the latest version of Cadimage from the official vendor website or trusted software distribution channel
- Close all instances of IrfanView and any applications using the CADImage plugin
- Run the Cadimage installer and follow the prompts to complete the upgrade
- Verify the installed version is 15.0.0.8 or higher after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7319 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-7319 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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