# CVE-2026-7718: Totolink WA300 POST Request cstecgi.cgi setWebWlanIdx command injection

> Remote attackers can execute arbitrary commands on Totolink WA300 routers via the webWlanIdx parameter in the cstecgi.cgi handler.

- **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
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 May 2026
- **Updated:** 5 May 2026
- **Also known as:** GHSA-7ww3-945v-369q

## What is CVE-2026-7718?

CVE-2026-7718 is a medium-severity command injection vulnerability in Totolink WA300, published on 4 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was identified in Totolink WA300 5.2cu.7112_B20190227. Impacted is the function setWebWlanIdx of the file /cgi-bin/cstecgi.cgi of the component POST Request Handler. The manipulation of the argument webWlanIdx leads to command injection. The attack may be initiated remotely. The exploit is publicly available and might be used.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2026-7718 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7718 is a medium-severity command injection vulnerability in Totolink WA300, published on 4 May 2026. 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-2026-7718 exists.

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

## Sources

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

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