CVE-2025-7293
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-26229.
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 during DXF file parsing, leading to memory corruption. A remote attacker can exploit this by tricking a user into opening a malicious DXF file, allowing execution of 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.
-
Confirm CADImage plugin installationSearch for CADImage-related DLL files in the IrfanView plugins directory (typically \Program Files\IrfanView\Plugins or \Program Files (x86)\IrfanView\Plugins). Look for files named CadImage.dll, CADImage.dll, or similar CAD-related plugins.Affected if CADImage DLL file is present in the plugins folder
-
Identify CADImage plugin versionRight-click the CADImage DLL file and select Properties, then navigate to the Details tab to view the File Version. Alternatively, use PowerShell: Get-Item 'C:\Program Files\IrfanView\Plugins\*.dll' | Select-Object Name, VersionInfo to list versions.Affected if File version is lower than 15.0.0.8 or the version field is empty/unavailable
-
Check if DXF file associations existOpen Control Panel > Default Programs > Set Associations and look for .dxf file type. Alternatively, check the IrfanView options (File > Properties/Types) to see if DXF is listed as an associated format.Affected if DXF files are associated with IrfanView or DXF appears in IrfanView's supported file types list
-
Verify CADImage plugin is loadedOpen Task Manager, go to Details tab, locate irfanview.exe, right-click and select 'Analyze wait chain' or use Process Explorer to check loaded modules. Look for CADImage-related DLLs under the IrfanView process.Affected if CADImage DLL is loaded in memory while IrfanView is running
-
Check for recent DXF file accessOpen Windows Event Viewer > Security logs and filter by Event ID 4656 or 4663, looking for recent access to .dxf files. Alternatively, check Windows prefetch or recent documents for DXF file openings.Affected if Any DXF files have been opened using IrfanView recently
The environment is affected if the CADImage plugin DLL is installed with a version prior to 15.0.0.8 and DXF file support is enabled or DXF files have been opened with IrfanView.
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.
From vendor data15.0.0.8
Avoid opening untrusted DXF files until a patch is available; consider disabling or removing the CADImage plugin if CAD rendering is not required.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7293 — 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-7293 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