# CVE-2026-7633: Totolink N300RH cstecgi.cgi setUploadSetting file inclusion

> Remote attackers can exploit a file inclusion vulnerability in the Totolink N300RH router's CGI interface to execute arbitrary code or read sensitive files.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2026
- **Updated:** 4 May 2026
- **Also known as:** GHSA-q632-88qp-5p5h

## What is CVE-2026-7633?

CVE-2026-7633 is a medium-severity path traversal vulnerability in Totolink N300RH, published on 2 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was identified in Totolink N300RH 6.1c.1353_B20190305. This impacts the function setUploadSetting of the file /cgi-bin/cstecgi.cgi. Such manipulation of the argument FileName leads to file inclusion. The attack may be performed from remote. The exploit is publicly available and might be used.

Weakness: CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2026-7633?


## How do I fix CVE-2026-7633?

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

## Is CVE-2026-7633 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7633 and fix it if it is affected.

What it is: CVE-2026-7633 is a medium-severity path traversal vulnerability in Totolink N300RH, published on 2 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7633 exists.

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

## Sources

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

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