# CVE-2023-30237: Code injection in n/a

> An attacker can execute arbitrary code via DLL injection in the CyberGhostVPN Windows client, requiring an upgrade to the latest version.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 May 2023
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-mrqj-9348-x8h5

## What is CVE-2023-30237?

CVE-2023-30237 is a high-severity code injection vulnerability in n/a, published on 9 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

CyberGhostVPN Windows Client before v8.3.10.10015 was discovered to contain a DLL injection vulnerability via the component Dashboard.exe.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2023-30237?

It affects 1 product.


Products: Cyberghostvpn Cyberghost.

## How do I fix CVE-2023-30237?

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

## Is CVE-2023-30237 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-30237 exists.

## Other vulnerabilities in n/a

- [CVE-2018-10646](https://insights.sbomify.com/CVE-2018-10646/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-30237 and fix it if it is affected.

What it is: CVE-2023-30237 is a high-severity code injection vulnerability in n/a, published on 9 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-30237 exists.

Affected product: n/a. 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-2023-30237/ (Markdown: https://insights.sbomify.com/CVE-2023-30237/index.md)
```

## Sources

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

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