# CVE-2026-4163: Wavlink WL-WN579A3 POST Request wireless.cgi GuestWifi command injection

> Remote attackers can execute arbitrary commands on Wavlink WL-WN579A3 routers via the wireless.cgi GuestWifi handler.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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:** 14 Mar 2026
- **Updated:** 17 Mar 2026
- **Also known as:** GHSA-pgmv-83cp-gpc7

## What is CVE-2026-4163?

CVE-2026-4163 is a critical command injection vulnerability in Wavlink WL-WN579A3, published on 14 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was detected in Wavlink WL-WN579A3 220323. This issue affects the function SetName/GuestWifi of the file /cgi-bin/wireless.cgi of the component POST Request Handler. Performing a manipulation results in command injection. It is possible to initiate the attack remotely. The exploit is now public and may be used. Upgrading the affected component is recommended.

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


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

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

## Is CVE-2026-4163 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4163 is a critical command injection vulnerability in Wavlink WL-WN579A3, published on 14 Mar 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-4163 exists.

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

## Sources

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

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