# CVE-2026-120195: WAVLINK WL-WN579A3-A Initial Setup Wizard adm.cgi set_wzdgwMesh os command injection


- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 1 Nov 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-3wx6-ffgj-fwjg

## What is CVE-2026-120195?

CVE-2026-120195 is a critical vulnerability in WAVLINK WL-WN579A3-A, published on 1 Nov 2026. 

### Official description

A security vulnerability has been detected in WAVLINK WL-WN579A3-A 2026-03-10-94f93d4. The impacted element is the function set_wzdgwMesh of the file /cgi-bin/adm.cgi of the component Initial Setup Wizard. The manipulation of the argument wlan_ssid leads to os command injection. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

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


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

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

## Is CVE-2026-120195 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120195 is a critical vulnerability in WAVLINK WL-WN579A3-A, published on 1 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120195 exists.

Affected product: WAVLINK WL-WN579A3-A. 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-120195/ (Markdown: https://insights.sbomify.com/CVE-2026-120195/index.md)
```

## Sources

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

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