CVE-2025-7238
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 DXF 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 DXF 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-26084.
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 confidenceAn out-of-bounds write vulnerability exists in the IrfanView CADImage Plugin's DXF file parser due to insufficient validation of user-supplied data. The flaw allows writing past the end of an allocated buffer during DXF parsing, enabling remote code execution in the context of the current process when a user opens a malicious DXF 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.
-
Locate the CADImage plugin fileSearch the IrfanView installation directory (commonly C:\Program Files\IrfanView or C:\Program Files (x86)\IrfanView) for plugin files related to CAD or DXF support, typically named CadImage.dll, CADImage.idf, or similar CADImage plugin files.Affected if The CADImage plugin file exists in the IrfanView plugins directory.
-
Determine the CADImage plugin versionRight-click the CADImage plugin file, select Properties, and check the File Version or Product Version field in the Details tab. Alternatively, use a tool like exiftool or examine the file's version info programmatically.Affected if The reported version number is less than 15.0.0.8 (for example, 15.0.0.7, 14.x, or earlier).
-
Verify IrfanView loads the CADImage pluginOpen IrfanView, go to Image menu and check if CAD/DXF file types are recognized, or attempt to open a DXF file to see if IrfanView uses the CADImage plugin to render it. You can also check Help > About Plugins to list loaded plugins.Affected if IrfanView successfully opens DXF files using the CADImage plugin, indicating the plugin is active.
A user is affected if the CADImage plugin is installed and loaded by IrfanView with a version number lower than 15.0.0.8, enabling the vulnerable DXF parser to be invoked when opening malicious 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 the vendor patch for the CADImage plugin when available. Until then, avoid opening untrusted DXF files and consider disabling or removing the CADImage plugin if DXF viewing is not required.
Cadimage version 15.0.0.8 or later
- 1. Identify the installed Cadimage plugin version by opening IrfanView and checking the 'Help' > 'About Plugins' menu, or by locating the cadimage.dll file in the IrfanView plugins directory and viewing its properties.
- 2. If the installed version is below 15.0.0.8, download the latest Cadimage plugin version (15.0.0.8 or later) from the official vendor website or IrfanView's plugin distribution page.
- 3. Close IrfanView completely before updating the plugin.
- 4. Navigate to the IrfanView plugins directory (typically C:\Program Files\IrfanView\Plugins or C:\Program Files (x86)\IrfanView\Plugins).
- 5. Backup the existing cadimage.dll file by copying it to a safe location.
- 6. Replace the existing cadimage.dll with the new version 15.0.0.8 or later.
- 7. Restart IrfanView and verify the plugin version through 'Help' > 'About Plugins' to confirm the update was successful.
- 8. Avoid opening untrusted DXF files, particularly from unknown or untrusted sources, as a secondary precaution until the upgrade is complete.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.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,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7238 — 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-7238 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