# CVE-2019-19356: Netis WF2419 Devices Remote Code Execution

> Authenticated attackers can execute arbitrary system commands as root via the router's tracert diagnostic tool due to insufficient input sanitization.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Feb 2020
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-ch88-rxpc-5c5r

## What is CVE-2019-19356?

CVE-2019-19356 is a high-severity command injection vulnerability in n/a, published on 7 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Netis WF2419 is vulnerable to authenticated Remote Code Execution (RCE) as root through the router Web management page. The vulnerability has been found in firmware version V1.2.31805 and V2.2.36123. After one is connected to this page, it is possible to execute system commands as root through the tracert diagnostic tool because of lack of user input sanitizing.

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

## Which versions are affected by CVE-2019-19356?

It affects 1 product.


Products: Netis-Systems Wf2419 Firmware.

## How do I fix CVE-2019-19356?

No fix has been published for CVE-2019-19356 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2019-19356 being exploited?

Yes. Attackers have exploited CVE-2019-19356 in the wild since at least 3 Nov 2021.

Public exploit code:

- Netis router RCE exploit ( CVE-2019-19356) (github_poc): https://github.com/shadowgatt/CVE-2019-19356
- https://github.com/qq1515406085/CVE-2019-19356 (github_poc): https://github.com/qq1515406085/CVE-2019-19356

## Other vulnerabilities in n/a

- [CVE-2018-6391](https://insights.sbomify.com/CVE-2018-6391/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-5967](https://insights.sbomify.com/CVE-2018-5967/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2018-6190](https://insights.sbomify.com/CVE-2018-6190/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-19356 and fix it if it is affected.

What it is: CVE-2019-19356 is a high-severity command injection vulnerability in n/a, published on 7 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2019-19356 in the wild since at least 3 Nov 2021.

Affected product: n/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-2019-19356/ (Markdown: https://insights.sbomify.com/CVE-2019-19356/index.md)
```

## Sources

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

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