CVE-2025-7251
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-26108.
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 confidenceOut-of-bounds read vulnerability in IrfanView CADImage Plugin's DWG file parser due to insufficient validation of user-supplied data during file parsing, allowing read past the end of an allocated buffer which can be leveraged for remote code execution.
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.
-
Locate the CADImage plugin installationFind the IrfanView plugins folder (typically C:\Program Files\IrfanView\Plugins or similar) and look for the CADImage plugin file (commonly cadimage.dll or similar CADImage-related DLL)Affected if The CADImage plugin DLL is present in the IrfanView plugins directory
-
Determine the installed CADImage plugin versionRight-click the CADImage plugin DLL, select Properties, and check the File Version or Product Version field in the Details tabAffected if The reported version number is lower than 15.0.0.8 (for example, 15.0.0.7 or earlier)
-
Verify the plugin is loaded by IrfanViewOpen IrfanView, go to Image menu and attempt to open a DWG file, or check if DWG file types are associated with IrfanView and the CADImage plugin is handling themAffected if DWG files can be opened through IrfanView using the CADImage plugin, indicating the plugin is active
-
Confirm DWG file handling capabilityCheck IrfanView menu options or file type associations to confirm DWG files are processed through the CADImage plugin rather than a different handlerAffected if IrfanView is configured to open DWG files using the CADImage plugin module
A system is affected if the CADImage plugin version is below 15.0.0.8 AND the plugin is installed and enabled for handling DWG files in IrfanView.
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 DWG files or disable the CADImage plugin until a vendor patch is available; implement input validation and bounds checking in DWG parsing routines.
Cadimage 15.0.0.8 or later
- Verify current Cadimage plugin version in IrfanView
- Download Cadimage version 15.0.0.8 or later from the official vendor
- Close IrfanView if currently running
- Install the updated Cadimage plugin
- Restart IrfanView and verify the new version is loaded
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
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 locallyCheck whether your project pulls in CVE-2025-7251 — 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-7251 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