CVE-2025-7247
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 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 DXF 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-26096.
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 for IrfanView contains an out-of-bounds read vulnerability when parsing DXF files due to insufficient validation of user-supplied data, allowing an attacker to read past the end of an allocated buffer and potentially achieve code execution in the current process context.
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 installationSearch for CADImage DLL files (cadimage.dll, CadImagePlugin.dll) in common IrfanView plugin directories: C:\Program Files\IrfanView\Plugins\ or C:\Program Files (x86)\IrfanView\Plugins\Affected if CADImage plugin DLL files are found in the IrfanView plugins folder
-
Determine installed CADImage versionRight-click the CADImage DLL file, select Properties, then view the Details tab for Product Version or File Version. Alternatively, right-click the DLL, select Properties > Digital Signatures to check signing information.Affected if Version is present but reports less than 15.0.0.8, or no version information is available
-
Verify DXF file handling capabilityOpen IrfanView, go to Options > Properties/Settings > Plugins. Check if CADImage plugin is loaded and enabled. Look for DXF file type association in IrfanView's file type settings.Affected if CADImage plugin is listed as loaded/enabled and DXF files are associated with IrfanView
-
Check for recent plugin activity or cacheExamine IrfanView's recent files list or temporary folders (e.g., %TEMP%\IrfanView) for recently opened DXF files that may have been processed by the plugin.Affected if DXF files have been opened recently using IrfanView with CADImage plugin present
The environment is affected if the CADImage plugin for IrfanView is installed with a version prior to 15.0.0.8 and is enabled for handling DXF 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-provided patch for CADImage plugin when available; avoid opening untrusted DXF files and consider disabling the plugin if not required.
Cadimage 15.0.0.8 or later
- Locate the CADImage plugin installation on the system
- Download CADImage version 15.0.0.8 or later from the official vendor (Cadimage)
- Update the CADImage plugin to version 15.0.0.8 or newer
- Restart IrfanView if it was running during the update
- Verify the plugin version shows 15.0.0.8 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7247 — 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-7247 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