# CVE-2024-22729: Command injection in n/a

> An attacker can execute arbitrary commands on the NETIS MW5360 router via the login page password parameter.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jan 2024
- **Updated:** 4 Jun 2025
- **Also known as:** GHSA-vqxw-rw4p-r6vh

## What is CVE-2024-22729?

CVE-2024-22729 is a critical command injection vulnerability in n/a, published on 25 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NETIS SYSTEMS MW5360 V1.0.1.3031 was discovered to contain a command injection vulnerability via the password parameter on the login page.

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

## Which versions are affected by CVE-2024-22729?

It affects 1 product.


Products: Netis-Systems Mw5360 Firmware.

## How do I fix CVE-2024-22729?

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

## Is CVE-2024-22729 being exploited?

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

Public exploit code:

- Netis router MW5360 unauthenticated RCE. (metasploit)
- Netis MW5360 V1.0.1.3031 - Command Injection (nuclei): http/cves/2024/CVE-2024-22729.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22729 and fix it if it is affected.

What it is: CVE-2024-22729 is a critical command injection vulnerability in n/a, published on 25 Jan 2024. 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-2024-22729 exists.

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-2024-22729/ (Markdown: https://insights.sbomify.com/CVE-2024-22729/index.md)
```

## Sources

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

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