# CVE-2025-8938: TOTOLINK N350R Telnet Service formSysTel backdoor


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 14 Aug 2025
- **Updated:** 15 Aug 2025
- **Also known as:** GHSA-3cc5-q36c-j82w

## What is CVE-2025-8938?

CVE-2025-8938 is a medium-severity vulnerability in TOTOLINK N350R, published on 14 Aug 2025. 

### Official description

A vulnerability was found in TOTOLINK N350R 1.2.3-B20130826. This issue affects the function formSysTel of the file /boafrm/formSysTel of the component Telnet Service. The manipulation of the argument TelEnabled leads to backdoor. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-912 (Hidden Functionality)

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

It affects 1 product.


Products: Totolink N350r Firmware.

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

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

## Is CVE-2025-8938 being exploited?

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

## Other vulnerabilities in TOTOLINK N350R

- [CVE-2025-8937](https://insights.sbomify.com/CVE-2025-8937/): TOTOLINK N350R formSysCmd command injection (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8938 is a medium-severity vulnerability in TOTOLINK N350R, published on 14 Aug 2025. 
Exploitation: There is no known exploitation of CVE-2025-8938 in the wild and no public exploit code.

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

## Sources

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

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