CVE-2025-7303
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 DWG 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 DWG 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-26384.
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 confidenceA memory corruption vulnerability exists in the IrfanView CADImage Plugin's DWG file parser due to insufficient validation of user-supplied data during file parsing. This lack of bounds checking allows attackers to corrupt memory and achieve arbitrary code execution in the context of the current process by tricking users into opening malicious DWG files.
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.
-
Verify IrfanView installationCheck if IrfanView is installed on the system by looking for the application in standard program directories or via system inventory tools.Affected if IrfanView is installed and the CADImage plugin is present
-
Locate the CADImage plugin filesSearch for files named CADImage or related to the CADImage plugin within the IrfanView plugins directory (typically found in the program's Plugins or Plugins32 folder).Affected if CADImage plugin files exist in the IrfanView installation directory
-
Determine Cadimage component versionRight-click the Cadimage DLL or related component, select Properties, and check the File Version field. Alternatively, use a version detection tool or script to query the file version of the Cadimage component.Affected if The Cadimage component version is lower than 15.0.0.8 or the version cannot be determined (indicating an unpatched older release)
-
Confirm DWG file handling is enabledCheck IrfanView's plugin configuration or file association settings to determine if the CADImage plugin is enabled for handling DWG file types.Affected if The CADImage plugin is enabled and configured to handle DWG files
The system is affected if IrfanView with the CADImage plugin (Cadimage component version below 15.0.0.8) is installed and configured to process DWG 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
Update the IrfanView CADImage Plugin to the latest patched version. Until a patch is available, restrict handling of untrusted DWG files and disable the plugin if not required.
Cadimage 15.0.0.8 or later
- Identify the CADImage plugin installation on systems running IrfanView
- Check the current version of the CADImage plugin (likely found in IrfanView's plugin directory or Add-ons section)
- Download Cadimage version 15.0.0.8 or later from the official vendor (Cadimage/IrfanView channels)
- Replace the existing CADImage plugin files with the updated version
- Restart IrfanView and verify the plugin loads correctly with the new version
- Alternatively, ensure IrfanView is updated to a version that bundles the fixed CADImage plugin (15.0.0.8+)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7303 — 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-7303 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