CVE-2025-7294
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 Memory Corruption 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 memory corruption condition. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-26230.
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 during DXF file parsing, leading to memory corruption. An attacker can exploit this by tricking a user into opening a specially crafted malicious DXF file, potentially achieving arbitrary code execution within the context of the user's 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 installationCheck the IrfanView plugins folder (typically C:\Program Files\IrfanView\Plugins or C:\Program Files (x86)\IrfanView\Plugins) for CadImage or CADImage related DLL files such as CadImage.dll, CADImagePlugin.dll, or similar naming patterns.Affected if The CADImage plugin DLL files are present in the IrfanView plugins directory.
-
Determine the CADImage plugin versionRight-click on the CADImage plugin DLL file, select Properties, then go to the Details tab to view the File Version. Alternatively, right-click the DLL, select Properties > Digital Signatures (if signed), or use a tool like ExifTool or a PE viewer to extract version metadata.Affected if The reported version is lower than 15.0.0.8, or no version information is available (which may indicate an old vulnerable version).
-
Verify IrfanView is using the CADImage plugin for DXF filesOpen IrfanView, go to Options > Properties/Settings > Plugins, or attempt to open a DXF file to see if it attempts to use the CADImage plugin for rendering. Check File > Open with any DXF file to trigger plugin loading.Affected if IrfanView loads or attempts to load the CADImage plugin when opening DXF files.
-
Check for recent DXF file activityReview Windows Event Logs (Application log) for IrfanView errors or crash reports related to DXF files, or check recent file access timestamps on DXF files that may have been opened.Affected if DXF files have been opened using IrfanView with the CADImage plugin, indicating the vulnerable code path has been executed.
You are affected if the CADImage plugin version is below 15.0.0.8 and the plugin is present and functional in your IrfanView installation, as this enables the vulnerable DXF parsing code to be executed.
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
Restrict or disable the CADImage plugin until an official vendor patch is available, and instruct users to never open untrusted DXF files from unknown sources.
Cadimage 15.0.0.8 or later
- Obtain Cadimage plugin version 15.0.0.8 or later from the official vendor
- Uninstall the current Cadimage plugin version
- Install the updated Cadimage plugin version 15.0.0.8 or newer
- Verify the installed version matches the fixed release
- Restart IrfanView if it was running during the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7294 — 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-7294 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