# CVE-2018-25260: MAGIX Music Editor 3.1 Buffer Overflow via SEH

> Local attackers can execute arbitrary code in MAGIX Music Editor by exploiting a buffer overflow in the FreeDB Proxy Options dialog via crafted input.

- **Severity:** High 8.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 22 Apr 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-v7hp-94p6-2c2c

## What is CVE-2018-25260?

CVE-2018-25260 is a high-severity memory corruption vulnerability in MAGIX Music Editor, published on 22 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

MAGIX Music Editor 3.1 contains a buffer overflow vulnerability in the FreeDB Proxy Options dialog that allows local attackers to execute arbitrary code by exploiting structured exception handling. Attackers can craft a malicious payload, paste it into the Server field via the CD menu's FreeDB Proxy Options, and trigger code execution when settings are accepted.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2018-25260?

It affects 1 product.


Products: Magix Music Editor Deluxe.

## How do I fix CVE-2018-25260?

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

## Is CVE-2018-25260 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25260 and fix it if it is affected.

What it is: CVE-2018-25260 is a high-severity memory corruption vulnerability in MAGIX Music Editor, published on 22 Apr 2026. 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-2018-25260 exists.

Affected product: MAGIX Music Editor. 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-2018-25260/ (Markdown: https://insights.sbomify.com/CVE-2018-25260/index.md)
```

## Sources

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

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