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

> Remote attackers can execute arbitrary OS commands with root privileges on NRadio N8-180 devices via crafted input in radio name parameters.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Feb 2025
- **Updated:** 18 Mar 2025
- **Also known as:** GHSA-m8mv-xfjj-7m87

## What is CVE-2024-53942?

CVE-2024-53942 is a medium-severity command injection vulnerability in n/a, published on 3 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on NRadio N8-180 NROS-1.9.2.n3.c5 devices. The /cgi-bin/luci/nradio/basic/radio endpoint is vulnerable to command injection via the 2.4 GHz and 5 GHz name parameters, allowing a remote attacker to execute arbitrary OS commands on the device (with root-level permissions) via crafted input.

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

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


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

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

## Is CVE-2024-53942 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-53942 is a medium-severity command injection vulnerability in n/a, published on 3 Feb 2025. 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-53942 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-53942/ (Markdown: https://insights.sbomify.com/CVE-2024-53942/index.md)
```

## Sources

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

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