# CVE-2025-70521: Command injection in n/a

> Unauthenticated attackers can inject commands via the diagnostic ping tool to execute arbitrary code on the device.

- **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:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-rv2w-876m-ggq4

## What is CVE-2025-70521?

CVE-2025-70521 is a critical command injection vulnerability in n/a, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The management portal's diagnostic ping tool of Fanvil x7a firmware version 2.6.0.1182 does not handle user supplied input securely. The lack of secure user input handling allows any unauthenticated attacker to inject commands and run code in the underlying Android operating system.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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


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

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

## Is CVE-2025-70521 being exploited?

There is no known exploitation of CVE-2025-70521 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-70521 is a critical command injection vulnerability in n/a, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-70521 in the wild and no public exploit code.

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-70521/ (Markdown: https://insights.sbomify.com/CVE-2025-70521/index.md)
```

## Sources

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

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