# CVE-2025-25940: Deserialization in n/a

> VisiCut allows remote code execution via insecure XML deserialization when loading PLF files, requiring users to upgrade to a patched version.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Mar 2025
- **Updated:** 12 Mar 2025
- **Also known as:** GHSA-9qjm-v45h-7fxq

## What is CVE-2025-25940?

CVE-2025-25940 is a critical unsafe deserialization vulnerability in n/a, published on 10 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

VisiCut 2.1 allows code execution via Insecure XML Deserialization in the loadPlfFile method of VisicutModel.java.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Visicut Visicut.

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

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

## Is CVE-2025-25940 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-43708](https://insights.sbomify.com/CVE-2025-43708/): Denial of service in VisiCut (low 3.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-25940 is a critical unsafe deserialization vulnerability in n/a, published on 10 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25940 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-25940/ (Markdown: https://insights.sbomify.com/CVE-2025-25940/index.md)
```

## Sources

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

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