# CVE-2026-28773: Authenticated OS Command Injection via Ping Utility Leading to RCE as Root

> Authenticated attackers can execute arbitrary shell commands as root via the Ping utility in IDC SFX Series satellite receivers.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **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:** 4 Mar 2026
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-c5hc-24j8-ggj4

## What is CVE-2026-28773?

CVE-2026-28773 is a critical command injection vulnerability in International Datacasting Corporation (IDC) SFX Series SuperFlex SatelliteReceiver Web Management Interface, published on 4 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The web-based Ping diagnostic utility (/IDC_Ping/main.cgi) in International Datacasting Corporation (IDC) SFX Series SuperFlex Satellite  Receiver Web Management Interface version 101 is vulnerable to OS Command Injection. The application insecurely parses the `IPaddr` parameter. An authenticated attacker can bypass server-side semicolon exclusion checks by using alternate shell metacharacters (such as the pipe `|` operator) to append and execute arbitrary shell commands with root privileges.

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

## Which versions are affected by CVE-2026-28773?

It affects 1 product.


Products: Datacast Sfx2100 Firmware.

## How do I fix CVE-2026-28773?

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

## Is CVE-2026-28773 being exploited?

There is no known exploitation of CVE-2026-28773 in the wild and no public exploit code.

## Other vulnerabilities in International Datacasting Corporation (IDC) SFX Series SuperFlex SatelliteReceiver Web Management Interface

- [CVE-2026-28775](https://insights.sbomify.com/CVE-2026-28775/): Unauthenticated RCE via SNMP Default Writable Community String (critical 10.0)
- [CVE-2026-28774](https://insights.sbomify.com/CVE-2026-28774/): Authenticated OS Command Injection via Traceroute Utility leads to Root RCE (critical 9.3)
- [CVE-2026-29127](https://insights.sbomify.com/CVE-2026-29127/): Incorrect Permission Assignment(777) on `monitor` Users Home Directory Containing SUID Root Binaries in IDC SFX2100 (critical 9.2)
- [CVE-2026-28777](https://insights.sbomify.com/CVE-2026-28777/): Hardcoded and Insecure Credentials for "User" Local Account with SSH Access On IDC SFX2100 Satellite Receiver (critical 9.2)
- [CVE-2026-29120](https://insights.sbomify.com/CVE-2026-29120/): Insecure, Hardcoded Root Password Stored in Anaconda Configuration File On IDC SFX2100 Satellite Receiver (critical 9.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-28773 and fix it if it is affected.

What it is: CVE-2026-28773 is a critical command injection vulnerability in International Datacasting Corporation (IDC) SFX Series SuperFlex SatelliteReceiver Web Management Interface, published on 4 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-28773 in the wild and no public exploit code.

Affected product: International Datacasting Corporation (IDC) SFX Series SuperFlex SatelliteReceiver Web Management Interface. 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-2026-28773/ (Markdown: https://insights.sbomify.com/CVE-2026-28773/index.md)
```

## Sources

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

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