# CVE-2025-64053: Memory corruption in n/a

> Attackers can cause denial of service or execute arbitrary commands on Fanvil x210 devices via a crafted POST request.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 5 Dec 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-pjqp-6rr5-xgrq

## What is CVE-2025-64053?

CVE-2025-64053 is a high-severity memory corruption vulnerability in n/a, published on 5 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Buffer overflow vulnerability on Fanvil x210 2.12.20 devices allows attackers to cause a denial of service or potentially execute arbitrary commands via crafted POST request to the /cgi-bin/webconfig?page=upload&action=submit endpoint.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Fanvil X210 Firmware.

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

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

## Is CVE-2025-64053 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-64055](https://insights.sbomify.com/CVE-2025-64055/): Auth bypass in n/a (critical 9.8)
- [CVE-2025-64054](https://insights.sbomify.com/CVE-2025-64054/): Cross-site scripting in n/a (critical 9.6)
- [CVE-2025-64057](https://insights.sbomify.com/CVE-2025-64057/): Path traversal in n/a (high 8.3)
- [CVE-2025-64052](https://insights.sbomify.com/CVE-2025-64052/): Command injection in n/a (medium 5.1)
- [CVE-2025-64056](https://insights.sbomify.com/CVE-2025-64056/): File upload in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-64053 is a high-severity memory corruption vulnerability in n/a, published on 5 Dec 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-64053 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-64053/ (Markdown: https://insights.sbomify.com/CVE-2025-64053/index.md)
```

## Sources

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

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