# CVE-2025-63952: Cross-site request forgery in n/a

> Attackers can create arbitrary accounts via CSRF in Magewell Pro Convert, potentially leading to unauthorized access.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Nov 2025
- **Updated:** 24 Nov 2025
- **Also known as:** GHSA-qf6c-fm2q-4fvw

## What is CVE-2025-63952?

CVE-2025-63952 is a medium-severity vulnerability in n/a, published on 24 Nov 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A Cross-Site Request Forgery (CSRF) in the /mwapi?method=add-user component of Magewell Pro Convert v1.2.213 allows attackers to arbitrarily create accounts via a crafted GET request.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 13 products.


Products: Magewell Pro Convert 12g Sdi 4k Plus Firmware, Magewell Pro Convert Aes67 Firmware, Magewell Pro Convert Audio Dx Firmware, Magewell Pro Convert for Ndi to Aio Firmware, Magewell Pro Convert for Ndi to Hdmi 4k Firmware, Magewell Pro Convert for Ndi to Hdmi Firmware, Magewell Pro Convert for Ndi to Sdi Firmware, Magewell Pro Convert Hdmi 4k Plus Firmware, Magewell Pro Convert Hdmi Plus Firmware, Magewell Pro Convert Hdmi Tx Firmware, Magewell Pro Convert Sdi 4k Plus Firmware, Magewell Pro Convert Sdi Plus Firmware, Magewell Pro Convert Sdi Tx Firmware.

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

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

## Is CVE-2025-63952 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63952 is a medium-severity vulnerability in n/a, published on 24 Nov 2025. Any signed-in user can exploit it over the 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-63952 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-2025-63952/ (Markdown: https://insights.sbomify.com/CVE-2025-63952/index.md)
```

## Sources

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

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