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

> Remote authenticated attackers can execute arbitrary commands as root via command injection in the admin web console of Extron SMP and SME devices.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Apr 2025
- **Updated:** 18 Apr 2025
- **Also known as:** GHSA-prv3-9p5f-cqv2

## What is CVE-2024-50960?

CVE-2024-50960 is a high-severity command injection vulnerability in n/a, published on 15 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A command injection vulnerability in the Nmap diagnostic tool in the admin web console of Extron SMP 111 <=3.01, SMP 351 <=2.16, SMP 352 <= 2.16, and SME 211 <= 3.02, allows a remote authenticated attacker to execute arbitrary commands as root on the underlying operating system.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 4 products.


Products: Extron Sme 211 Firmware, Extron Smp 111 Firmware, Extron Smp 351 Firmware, Extron Smp 352 Firmware.

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

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

## Is CVE-2024-50960 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-50960 is a high-severity command injection vulnerability in n/a, published on 15 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-50960 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-50960/ (Markdown: https://insights.sbomify.com/CVE-2024-50960/index.md)
```

## Sources

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

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