CVE-2025-7324
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-26430.
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 an out-of-bounds read vulnerability. This allows attackers to read memory past the end of an allocated buffer, which can be leveraged to achieve remote code execution 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.
-
Locate the CADImage plugin fileOpen IrfanView installation directory and navigate to the 'Plugins' or 'Plugins32' folder. Look for a DLL file related to CAD or DXF support, typically named 'CADImage.dll' or similar.Affected if The CADImage.dll or CAD-related DLL is present in the plugins folder, indicating the plugin is installed
-
Check the CADImage plugin versionRight-click on the CADImage DLL file, select Properties, then go to the Details tab to view the File Version. Alternatively, use PowerShell: (Get-Item 'C:\Path\To\Plugins\CADImage.dll').VersionInfo.FileVersionAffected if The version number is lower than 15.0.0.8 (for example, 15.0.0.7, 14.x.x.x, or any version that does not match 15.0.0.8 or higher)
-
Confirm the plugin is activeOpen IrfanView, go to Options > Properties/Settings > Plugins. Look for the CAD/DXF plugin listed as loaded and enabled. Or check if the plugin DLL is not renamed with a disabled extension (like .dll.bak).Affected if The CADImage plugin appears as loaded/enabled in IrfanView's plugin list
-
Verify DXF file association or supportCheck if IrfanView can open or preview .dxf files, or if the plugin is associated with DXF file handling. In IrfanView, try Options > File types or check if .dxf appears in the list of supported image types.Affected if DXF file support is enabled and the CADImage plugin handles DXF parsing
If the CADImage plugin DLL is present in the IrfanView plugins folder with a version lower than 15.0.0.8, and DXF file support is enabled, the environment is vulnerable to this CVE.
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 or disable/remove the plugin until a patch is available; avoid opening untrusted DXF files from unknown sources.
Cadimage 15.0.0.8
- 1. Identify all systems with Cadimage (IrfanView CADImage Plugin) installed
- 2. Check current Cadimage version - look for version information in the plugin or IrfanView about dialog
- 3. If installed version is below 15.0.0.8, download Cadimage version 15.0.0.8 or later from the official vendor source
- 4. Back up any existing Cadimage installations and custom configurations
- 5. Install the upgraded Cadimage version 15.0.0.8
- 6. Verify the installed version now shows 15.0.0.8 or higher
- 7. Test that DXF files load correctly in IrfanView with the updated plugin
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7324 — 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-7324 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