# CVE-2026-7690: Wavlink WL-WN570HA1 adm.cgi set_sys_adm command injection

> Remote attackers can execute arbitrary commands via the Username parameter in the admin interface of unsupported Wavlink routers.

- **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:** 3 May 2026
- **Updated:** 4 May 2026
- **Also known as:** GHSA-6jr2-m439-xcmf

## What is CVE-2026-7690?

CVE-2026-7690 is a medium-severity command injection vulnerability in Wavlink WL-WN570HA1, published on 3 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A weakness has been identified in Wavlink WL-WN570HA1 R70HA1 V1410_221110. This issue affects the function set_sys_adm of the file /cgi-bin/adm.cgi. This manipulation of the argument Username causes command injection. It is possible to initiate the attack remotely. The exploit has been made available to the public and could be used for attacks. Once again the vendors acted very professional and confirms, "that the WN570HA1 firmware version R70HA1 V1410_221110 has been removed from our website." This vulnerability only affects products that are no longer supported by the maintainer.

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-7690?

It affects 1 product.


Products: Wavlink Wl-Wn570ha1 Firmware.

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

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

## Is CVE-2026-7690 being exploited?

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

## Other vulnerabilities in Wavlink WL-WN570HA1

- [CVE-2026-7691](https://insights.sbomify.com/CVE-2026-7691/): Wavlink WL-WN570HA1 adm.cgi set_sys_cmd command injection (medium 5.3)
- [CVE-2026-7692](https://insights.sbomify.com/CVE-2026-7692/): Wavlink WL-WN570HA1 adm.cgi ping_ddns command injection (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7690 is a medium-severity command injection vulnerability in Wavlink WL-WN570HA1, published on 3 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-7690 exists.

Affected product: Wavlink WL-WN570HA1. 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-7690/ (Markdown: https://insights.sbomify.com/CVE-2026-7690/index.md)
```

## Sources

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

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