# CVE-2026-28769: Path traversal in SFX Series SuperFlex Satellite Receiver Web management interface

> An authenticated attacker can exploit a path traversal flaw in the IDC SFX Series web interface to enumerate arbitrary files on the underlying filesystem.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/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-cxrh-ppvh-2gwm

## What is CVE-2026-28769?

CVE-2026-28769 is a medium-severity path traversal vulnerability in International Datacasting Corporation (IDC) SFX Series SuperFlex Satellite Receiver 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

A path traversal vulnerability exists in the /IDC_Logging/checkifdone.cgi script in International Datacasting Corporation (IDC) SFX Series SuperFlex Satellite Receiver Web management portal version 101. An authenticated attacker can manipulate the `file` parameter to traverse directories and enumerate arbitrary files on the underlying filesystem. Due to the insecure perl file path handling function in use, a authenticated actor is able to preform directory traversal, with the backup endpoint confirming a file exists by indicating that a backup operation was successful or when using the path of a non existent file, the returned status is failed.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Datacast Sfx2100 Firmware.

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

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

## Is CVE-2026-28769 being exploited?

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

## Other vulnerabilities in International Datacasting Corporation (IDC) SFX Series SuperFlex Satellite Receiver 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-28773](https://insights.sbomify.com/CVE-2026-28773/): Authenticated OS Command Injection via Ping Utility Leading to RCE as Root (critical 9.3)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-28769 is a medium-severity path traversal vulnerability in International Datacasting Corporation (IDC) SFX Series SuperFlex Satellite Receiver 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-28769 in the wild and no public exploit code.

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

## Sources

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

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