# CVE-2025-9149: Wavlink WL-NU516U1 wireless.cgi sub_4032E4 command injection

> Remote attackers can execute arbitrary commands on Wavlink WL-NU516U1 routers via the Guest_ssid parameter in wireless.cgi.

- **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:** 19 Aug 2025
- **Updated:** 19 Aug 2025
- **Also known as:** GHSA-8f9q-2v4r-6qgg

## What is CVE-2025-9149?

CVE-2025-9149 is a medium-severity command injection vulnerability in Wavlink WL-NU516U1, published on 19 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was determined in Wavlink WL-NU516U1 M16U1_V240425. This impacts the function sub_4032E4 of the file /cgi-bin/wireless.cgi. This manipulation of the argument Guest_ssid causes command injection. The attack is possible to be carried out remotely. The exploit has been publicly disclosed and may be utilized.

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-2025-9149?

It affects 1 product.


Products: Wavlink Wl-Nu516u1 Firmware.

## How do I fix CVE-2025-9149?

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

## Is CVE-2025-9149 being exploited?

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

## Other vulnerabilities in Wavlink WL-NU516U1

- [CVE-2026-3703](https://insights.sbomify.com/CVE-2026-3703/): Wavlink NU516U1 login.cgi sub_401A10 out-of-bounds write (critical 9.3)
- [CVE-2026-4861](https://insights.sbomify.com/CVE-2026-4861/): Wavlink WL-NU516U1 nas.cgi ftext stack-based overflow (high 8.7)
- [CVE-2026-3612](https://insights.sbomify.com/CVE-2026-3612/): Wavlink WL-NU516U1 OTA Online Upgrade adm.cgi sub_405AF4 command injection (high 8.6)
- [CVE-2026-3613](https://insights.sbomify.com/CVE-2026-3613/): Wavlink WL-NU516U1 login.cgi sub_401A0C stack-based overflow (high 8.6)
- [CVE-2026-2615](https://insights.sbomify.com/CVE-2026-2615/): Wavlink WL-NU516U1 firewall.cgi singlePortForwardDelete command injection (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-9149 and fix it if it is affected.

What it is: CVE-2025-9149 is a medium-severity command injection vulnerability in Wavlink WL-NU516U1, published on 19 Aug 2025. 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-2025-9149 exists.

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

## Sources

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

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