CVE-2025-7233
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 Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information 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 in conjunction with other vulnerabilities to execute arbitrary code in the context of the current process. Was ZDI-CAN-26072.
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 lacks proper validation of user-supplied data when parsing DWG files, leading to an out-of-bounds read that accesses memory beyond allocated buffers. This allows remote attackers to disclose sensitive information via malicious DWG files or pages requiring user interaction. The vulnerability can be chained with other flaws to achieve arbitrary 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 installationSearch for cadimage.dll or CADImage plugin files in the IrfanView plugins directory (typically C:\Program Files\IrfanView\Plugins or C:\Program Files (x86)\IrfanView\Plugins)Affected if The CADImage plugin file exists in the IrfanView plugins folder
-
Determine the CADImage plugin versionRight-click the CADImage plugin DLL file, select Properties, then navigate to the Details tab to view the File Version. Alternatively, check any version information file provided with the plugin installationAffected if The displayed version number is less than 15.0.0.8 (for example, 15.0.0.7 or earlier)
-
Verify DWG file association or preview capabilityOpen IrfanView and attempt to open a DWG file, or check if DWG files are listed in IrfanView's supported formats. Also verify if the CADImage plugin appears enabled in IrfanView's Properties or plugin list (Access Plugins > Properties/Configure in IrfanView)Affected if DWG files can be opened, previewed, or the CADImage plugin shows as active in IrfanView's plugin configuration
-
Inspect recently opened DWG filesCheck the IrfanView recent files list, temporary folders, or user-specified directories for any DWG files that may have been opened from untrusted sourcesAffected if DWG files from unknown or untrusted sources have been opened in IrfanView recently
You are affected if the CADImage plugin is installed and its version is below 15.0.0.8, with DWG file handling enabled and potential exposure to untrusted 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
Update the CADImage plugin to a patched version once available, or remove the plugin if unnecessary. Avoid opening untrusted DWG files from unknown sources.
Cadimage 15.0.0.8 or later
- Verify current Cadimage plugin version by opening IrfanView and checking Help > About Plugins or examining the cadimage.dll file properties
- Download Cadimage version 15.0.0.8 or later from the official vendor website
- Close all instances of IrfanView
- Install the updated Cadimage plugin following the vendor's installation instructions
- Restart IrfanView and verify the plugin loads correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.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 $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7233 — 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-7233 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