# CVE-2025-12213: Tenda O3 setVlanConfig GetValue stack-based overflow

> Remote attackers can trigger a stack-based buffer overflow in the Tenda O3 router's VLAN configuration interface, potentially leading to arbitrary code execution.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Oct 2025
- **Updated:** 24 Feb 2026
- **Also known as:** GHSA-fxm8-3753-c2p6

## What is CVE-2025-12213?

CVE-2025-12213 is a high-severity memory corruption vulnerability in Tenda O3, published on 27 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security vulnerability has been detected in Tenda O3 1.0.0.10(2478). This vulnerability affects the function SetValue/GetValue of the file /goform/setVlanConfig. Such manipulation of the argument lan leads to stack-based buffer overflow. The attack can be launched remotely. The exploit has been disclosed publicly and may be used.

Weakness: CWE-121 (Stack-based Buffer Overflow), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Tenda O3 Firmware1.0.0.10\(2478\).

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

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

## Is CVE-2025-12213 being exploited?

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

## Other vulnerabilities in Tenda O3

- [CVE-2025-12209](https://insights.sbomify.com/CVE-2025-12209/): Tenda O3 setDhcpConfig GetValue stack-based overflow (high 8.7)
- [CVE-2025-12210](https://insights.sbomify.com/CVE-2025-12210/): Tenda O3 AdvSetLanip GetValue stack-based overflow (high 8.7)
- [CVE-2025-12211](https://insights.sbomify.com/CVE-2025-12211/): Tenda O3 setDmzInfo GetValue stack-based overflow (high 8.7)
- [CVE-2025-12212](https://insights.sbomify.com/CVE-2025-12212/): Tenda O3 setNetworkService GetValue stack-based overflow (high 8.7)
- [CVE-2025-12214](https://insights.sbomify.com/CVE-2025-12214/): Tenda O3 sysAutoReboot GetValue stack-based overflow (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-12213 is a high-severity memory corruption vulnerability in Tenda O3, published on 27 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-12213 exists.

Affected product: Tenda O3. 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-12213/ (Markdown: https://insights.sbomify.com/CVE-2025-12213/index.md)
```

## Sources

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

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