CVE-2025-7258
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 Write 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 write 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-26127.
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 write operation past the end of an allocated buffer. This memory corruption can be triggered by convincing a user to open a specially crafted malicious DWG file, allowing attackers to execute arbitrary code 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.
-
Locate the CADImage plugin fileSearch for CADImage.dll in the IrfanView installation directory, typically under the 'Plugins' or 'Plugins32' subfolder. Common paths include C:\Program Files\IrfanView\Plugins\CADImage.dll or C:\Program Files (x86)\IrfanView\Plugins\CADImage.dll.Affected if The CADImage.dll file exists in the IrfanView Plugins folder, indicating the plugin is installed.
-
Determine the CADImage plugin versionRight-click the CADImage.dll file, select Properties, then go to the Details tab to view the File Version. Alternatively, use PowerShell: (Get-Item 'C:\Program Files\IrfanView\Plugins\CADImage.dll').VersionInfo.FileVersion (adjust path if different).Affected if The reported version number is less than 15.0.0.8 (for example, 15.0.0.7 or earlier).
-
Confirm IrfanView is installedCheck for IrfanView installation by looking for irfanview.exe in Program Files or Program Files (x86), or query the Windows registry under HKLM\SOFTWARE\IrfanView or HKLM\SOFTWARE\WOW6432Node\IrfanView.Affected if IrfanView is installed and the vulnerable CADImage plugin is present.
A user is affected if IrfanView with the CADImage plugin version below 15.0.0.8 is installed and the user opens DWG files using this plugin.
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
Users should avoid opening untrusted DWG files and refrain from visiting untrusted websites that may attempt to deliver malicious DWG content. Keep IrfanView and the CADImage plugin updated when patches become available, or disable the plugin if DWG viewing is not required.
Cadimage 15.0.0.8 or later
- Identify all systems running IrfanView with the Cadimage plugin
- Verify the installed Cadimage version is below 15.0.0.8
- Obtain Cadimage version 15.0.0.8 or later from the official vendor source
- Uninstall or replace the existing Cadimage plugin with the updated version
- Confirm the update was successful by checking the plugin version
- Test DWG file viewing functionality to ensure the plugin works correctly after the update
- Re-scan or reassess the affected systems to verify the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.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 $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7258 — 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-7258 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