# CVE-2025-4829: TOTOLINK A702R/A3002R/A3002RU HTTP POST Request formStats sub_40BE30 buffer overflow

> Remote attackers can trigger a buffer overflow in TOTOLINK routers via HTTP POST requests, potentially leading to code execution or service disruption.

- **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`)
- **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:** 17 May 2025
- **Updated:** 19 May 2025
- **Also known as:** GHSA-h9vw-8pf3-5j78

## What is CVE-2025-4829?

CVE-2025-4829 is a high-severity memory corruption vulnerability in Totolink A3002r Firmware, published on 17 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability classified as critical was found in TOTOLINK A702R, A3002R and A3002RU 3.0.0-B20230809.1615. Affected by this vulnerability is the function sub_40BE30 of the file /boafrm/formStats of the component HTTP POST Request Handler. The manipulation of the argument submit-url leads to buffer overflow. The attack can 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-4829?

It affects 3 products.


Products: Totolink A3002r Firmware, Totolink A3002ru Firmware, Totolink A702r Firmware.

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

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

## Is CVE-2025-4829 being exploited?

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

## Other vulnerabilities in Totolink A3002r Firmware

- [CVE-2025-55591](https://insights.sbomify.com/CVE-2025-55591/): Command injection in n/a (critical 9.8)
- [CVE-2025-45858](https://insights.sbomify.com/CVE-2025-45858/): Command injection in n/a (critical 9.8)
- [CVE-2025-45861](https://insights.sbomify.com/CVE-2025-45861/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-45863](https://insights.sbomify.com/CVE-2025-45863/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-45865](https://insights.sbomify.com/CVE-2025-45865/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4829 is a high-severity memory corruption vulnerability in Totolink A3002r Firmware, published on 17 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-4829 in the wild and no public exploit code.

Affected product: Totolink A3002r Firmware. 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-4829/ (Markdown: https://insights.sbomify.com/CVE-2025-4829/index.md)
```

## Sources

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

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