# CVE-2025-34123: VideoCharge Studio 2.12.3.685 SEH Buffer Overflow via .VSC File

> A stack-based buffer overflow in VideoCharge Studio allows arbitrary code execution when a user opens a malicious .VSC file.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 16 Jul 2025
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-rjrm-8wx5-683q

## What is CVE-2025-34123?

CVE-2025-34123 is a high-severity memory corruption vulnerability in VideoCharge Software Studio, published on 16 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

A stack-based buffer overflow vulnerability exists in VideoCharge Studio 2.12.3.685 when processing a specially crafted .VSC configuration file. The issue occurs due to improper handling of user-supplied data in the XML 'Name' attribute, leading to an SEH overwrite condition. An attacker can exploit this vulnerability by convincing a user to open a malicious .VSC file, resulting in arbitrary code execution under the context of the user.

Weakness: CWE-20 (Improper Input Validation), CWE-94 (Improper Control of Generation of Code), CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2025-34123 being exploited?

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

Public exploit code:

- VideoCharge Studio Buffer Overflow (SEH) (metasploit)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-34123 is a high-severity memory corruption vulnerability in VideoCharge Software Studio, published on 16 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-34123 exists.

Affected product: VideoCharge Software Studio. 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-34123/ (Markdown: https://insights.sbomify.com/CVE-2025-34123/index.md)
```

## Sources

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

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