CVE-2025-7265
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 CGM 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 CGM 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-26173.
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 suffers from an out-of-bounds read vulnerability when parsing CGM files due to insufficient validation of user-supplied data. The lack of bounds checking allows reading 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 fileSearch for 'CadImage' or 'CADImage' DLL files in the IrfanView installation directory, typically under a 'plugins' or 'plugins32' folder. Common names include CadImage.dll, CADImage.dll, or similar.Affected if The CADImage plugin DLL is present on the system
-
Check the installed plugin versionRight-click the CADImage DLL file, select Properties, then go to the Details tab to view the File Version or Product Version field.Affected if The version shown is lower than 15.0.0.8 (e.g., 15.0.0.7, 14.x.x.x, etc.)
-
Verify CGM file associationOpen IrfanView, go to Options > Properties/Settings > Plug-ins. Look for the CADImage plugin entry and confirm CGM file types are listed as supported extensions.Affected if CGM file support is enabled in the plugin configuration
-
Confirm plugin loads on IrfanView startupLaunch IrfanView and check the About window or the Plug-ins section in the application to see if the CADImage plugin is listed as loaded.Affected if The CADImage plugin appears as loaded or active in IrfanView
You are affected if the CADImage plugin is installed with a version lower than 15.0.0.8 AND CGM file support is enabled in 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.
dbcve · scoped15.0.0.8
Avoid opening untrusted or unverified CGM files until a patch is available from IrfanView. Consider disabling or removing the CADImage plugin for users who do not require CGM file support.
Cadimage version 15.0.0.8
- Check the current version of the Cadimage plugin installed on the system
- Navigate to the official Cadimage website or IrfanView plugin distribution page to obtain the fixed version
- Download Cadimage version 15.0.0.8 or later
- Backup any existing CADImage plugin files before upgrading
- Install or replace the existing Cadimage plugin files with version 15.0.0.8
- Restart IrfanView if it was running during the upgrade
- Verify the new version is correctly installed by checking the plugin version information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.0 h
- Testing4.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 $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7265 — 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-7265 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