# CVE-2025-30045: Code Injection in CGM CLININET


- **Severity:** High 8.6 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-rrrj-xjqg-m92h

## What is CVE-2025-30045?

CVE-2025-30045 is a high-severity vulnerability in CGM CLININET, published on 23 Oct 2026. 

### Official description

CGM CLININET is vulnerable to Code Injection in the ConvExpr function, which processes Perl expressions into RTF document content. Due to improper control of the code evaluated from these expressions, an authenticated, high-privileged attacker can cause arbitrary code to be executed with root privileges. 

The vulnerability was confirmed to affect versions up to 2026.MS3 but later versions may also be vulnerable.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2025-30045 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-30045 is a high-severity vulnerability in CGM CLININET, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2025-30045 in the wild and no public exploit code.

Affected product: CGM CLININET. 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-30045/ (Markdown: https://insights.sbomify.com/CVE-2025-30045/index.md)
```

## Sources

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

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