# CVE-2025-7213: FNKvision FNK-GU2 UART Interface on-chip debug and test interface with improper access control

> Physical attackers can exploit improper access control on the UART interface to gain unauthorized debug access and potentially execute code on the device.

- **Severity:** Medium 5.4 (`CVSS:4.0/AV:P/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **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:** 9 Jul 2025
- **Updated:** 9 Jul 2025
- **Also known as:** GHSA-2vhm-8pv3-vj8c

## What is CVE-2025-7213?

CVE-2025-7213 is a medium-severity missing authorization vulnerability in FNKvision FNK-GU2, published on 9 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability classified as critical has been found in FNKvision FNK-GU2 up to 40.1.7. Affected is an unknown function of the component UART Interface. The manipulation leads to on-chip debug and test interface with improper access control. It is possible to launch the attack on the physical device. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used.

Weakness: CWE-1191 (On-Chip Debug and Test Interface With Improper Access Control)

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


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

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

## Is CVE-2025-7213 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7213 is a medium-severity missing authorization vulnerability in FNKvision FNK-GU2, published on 9 Jul 2025. 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-2025-7213 exists.

Affected product: FNKvision FNK-GU2. 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-7213/ (Markdown: https://insights.sbomify.com/CVE-2025-7213/index.md)
```

## Sources

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

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