# CVE-2023-7187: Totolink N350RT HTTP POST Request stack-based overflow

> A stack-based buffer overflow in the HTTP POST handler allows attackers to execute arbitrary code on Totolink N350RT routers.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-w6vc-3rw3-4m6g

## What is CVE-2023-7187?

CVE-2023-7187 is a medium-severity memory corruption vulnerability in Totolink N350RT, published on 31 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in Totolink N350RT 9.3.5u.6139_B20201216. It has been rated as critical. This issue affects some unknown processing of the file /cgi-bin/cstecgi.cgi?action=login&flag=ie8 of the component HTTP POST Request Handler. The manipulation leads to stack-based buffer overflow. The exploit has been disclosed to the public and may be used. The identifier VDB-249389 was assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2023-7187?

It affects 1 product.


Products: Totolink N350rt Firmware.

## How do I fix CVE-2023-7187?

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

## Is CVE-2023-7187 being exploited?

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

## Other vulnerabilities in Totolink N350RT

- [CVE-2025-51630](https://insights.sbomify.com/CVE-2025-51630/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-42966](https://insights.sbomify.com/CVE-2024-42966/): Missing authorization in n/a (critical 9.8)
- [CVE-2024-7462](https://insights.sbomify.com/CVE-2024-7462/): TOTOLINK N350RT cstecgi.cgi setWizardCfg buffer overflow (high 8.7)
- [CVE-2024-7333](https://insights.sbomify.com/CVE-2024-7333/): TOTOLINK N350RT cstecgi.cgi setParentalRules buffer overflow (high 8.7)
- [CVE-2022-36479](https://insights.sbomify.com/CVE-2022-36479/): Command injection in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-7187 and fix it if it is affected.

What it is: CVE-2023-7187 is a medium-severity memory corruption vulnerability in Totolink N350RT, published on 31 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-7187 in the wild and no public exploit code.

Affected product: Totolink N350RT. 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-2023-7187/ (Markdown: https://insights.sbomify.com/CVE-2023-7187/index.md)
```

## Sources

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

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