# CVE-2025-7237: IrfanView CADImage Plugin DWG File Parsing Memory Corruption Remote Code Execution Vulnerability

> Remote attackers can execute arbitrary code by tricking users into opening malicious DWG files in the IrfanView CADImage Plugin.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Jul 2025
- **Updated:** 22 Jul 2025
- **Also known as:** GHSA-2wm3-m6j7-pxcp

## What is CVE-2025-7237?

CVE-2025-7237 is a high-severity memory corruption vulnerability in Cadsofttools Cadimage, published on 21 Jul 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

IrfanView 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-26083.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2025-7237?

It affects 1 product.


Products: Cadsofttools Cadimage.

## How do I fix CVE-2025-7237?

No fix has been published for CVE-2025-7237 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-7237 being exploited?

There is no known exploitation of CVE-2025-7237 in the wild and no public exploit code.

## Other vulnerabilities in Cadsofttools Cadimage

- [CVE-2025-7234](https://insights.sbomify.com/CVE-2025-7234/): IrfanView CADImage Plugin CGM File Parsing Out-of-Bounds Write Remote Code Execution Vulnerability (high 7.8)
- [CVE-2025-7235](https://insights.sbomify.com/CVE-2025-7235/): IrfanView CADImage Plugin DXF File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability (high 7.8)
- [CVE-2025-7236](https://insights.sbomify.com/CVE-2025-7236/): IrfanView CADImage Plugin DWG File Parsing Memory Corruption Remote Code Execution Vulnerability (high 7.8)
- [CVE-2025-7238](https://insights.sbomify.com/CVE-2025-7238/): IrfanView CADImage Plugin DXF File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability (high 7.8)
- [CVE-2025-7239](https://insights.sbomify.com/CVE-2025-7239/): IrfanView CADImage Plugin DWG File Parsing Memory Corruption Remote Code Execution Vulnerability (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-7237 and fix it if it is affected.

What it is: CVE-2025-7237 is a high-severity memory corruption vulnerability in Cadsofttools Cadimage, published on 21 Jul 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-7237 in the wild and no public exploit code.

Affected product: Cadsofttools Cadimage. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-7237/ (Markdown: https://insights.sbomify.com/CVE-2025-7237/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-7237
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-7237
- OSV: https://osv.dev/vulnerability/CVE-2025-7237

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-7237/
Summaries are generated and may contain mistakes; the official description above is the record.