# CVE-2025-5911: TOTOLINK EX1200T HTTP POST Request formDMZ buffer overflow

> Remote attackers can trigger a buffer overflow in the HTTP POST handler, potentially leading to arbitrary code execution on the device.

- **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:** 10 Jun 2025
- **Updated:** 10 Jun 2025
- **Also known as:** GHSA-qjqq-q9g6-p92r

## What is CVE-2025-5911?

CVE-2025-5911 is a high-severity memory corruption vulnerability in TOTOLINK EX1200T, published on 10 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in TOTOLINK EX1200T up to 4.1.2cu.5232_B20210713 and classified as critical. Affected by this issue is some unknown functionality of the file /boafrm/formDMZ of the component HTTP POST Request Handler. The manipulation leads to buffer overflow. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Totolink Ex1200t Firmware.

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

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

## Is CVE-2025-5911 being exploited?

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

## Other vulnerabilities in TOTOLINK EX1200T

- [CVE-2025-51451](https://insights.sbomify.com/CVE-2025-51451/): Auth bypass in n/a (critical 9.8)
- [CVE-2025-28038](https://insights.sbomify.com/CVE-2025-28038/): Command injection in n/a (critical 9.8)
- [CVE-2025-28039](https://insights.sbomify.com/CVE-2025-28039/): Command injection in n/a (critical 9.8)
- [CVE-2023-52032](https://insights.sbomify.com/CVE-2023-52032/): Command injection in n/a (critical 9.8)
- [CVE-2021-42884](https://insights.sbomify.com/CVE-2021-42884/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5911 is a high-severity memory corruption vulnerability in TOTOLINK EX1200T, published on 10 Jun 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-5911 exists.

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

## Sources

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

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