CVE-2025-7261
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-26130.
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. The plugin fails to properly validate user-supplied data during DWG parsing, allowing reads past the end of allocated buffers. This memory corruption can be leveraged for remote code execution in the context of the current process.
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.
-
Confirm IrfanView installationCheck for IrfanView installation directory (typically C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView)Affected if IrfanView is installed on the system
-
Locate CADImage pluginSearch for CADImage plugin DLL (cadimage.dll) in IrfanView\Plugins or IrfanView\Plugins32 directoryAffected if CADImage plugin DLL exists in the IrfanView plugins folder
-
Check CADImage plugin versionRight-click the CADImage DLL file, select Properties, and view the File Version or Product Version fieldAffected if The reported version is lower than 15.0.0.8 (e.g., 15.0.0.7, 14.x, etc.)
-
Verify plugin is loaded by IrfanViewOpen IrfanView, go to menu: Image > Properties, or check menu options for CAD/DWG file support under File > OpenAffected if DWG file types are recognized or the CADImage plugin is listed as active in IrfanView's plugin information (Menu > Help > Installed plugins)
-
Check for recent DWG file handlingReview recent file access logs, Windows Prefetch, or examine the IrfanView recent files list for .dwg file opensAffected if Untrusted or unknown DWG files have been opened using IrfanView with the CADImage plugin
The system is affected if IrfanView with the Cadsofttools CADImage plugin (version below 15.0.0.8) is installed and the plugin is enabled 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
Apply vendor patches for the CADImage plugin immediately. Until then, refrain from opening untrusted DWG files and consider disabling or removing the CADImage plugin if DWG viewing is not required.
Cadimage 15.0.0.8 or later
- Identify the current version of the Cadimage plugin installed in IrfanView by checking the plugin properties or version information
- Navigate to the official Cadimage vendor website or trusted distribution channel to obtain the latest version
- Download Cadimage version 15.0.0.8 or later
- Close IrfanView and any applications using the Cadimage plugin
- Run the installer for the updated Cadimage version and follow the installation prompts
- Restart IrfanView and verify the plugin version shows 15.0.0.8 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7261 — 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-7261 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