# CVE-2026-28772: Reflected XSS in IDC_Logging Index endpoint

> Remote attackers can execute arbitrary scripts via reflected XSS in the IDC SFX SuperFlex satellite receiver web interface.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Mar 2026
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-vp39-29pg-fg37

## What is CVE-2026-28772?

CVE-2026-28772 is a medium-severity cross-site scripting vulnerability in International Datacasting Corporation (IDC) SFX Series SuperFlex SatelliteReceiver Web Management Interface, published on 4 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A Reflected Cross-Site Scripting (XSS) vulnerability in the /IDC_Logging/index.cgi endpoint of International Datacasting Corporation (IDC) SFX Series SuperFlex SatelliteReceiver Web Management Interface version 101 allows a remote attacker to execute arbitrary web scripts or HTML. The vulnerability is triggered by sending a crafted payload through the `submitType` parameter, which is reflected directly into the DOM without proper escaping.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Datacast Sfx2100 Firmware.

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

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

## Is CVE-2026-28772 being exploited?

There is no known exploitation of CVE-2026-28772 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-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-28772 and fix it if it is affected.

What it is: CVE-2026-28772 is a medium-severity cross-site scripting vulnerability in International Datacasting Corporation (IDC) SFX Series SuperFlex SatelliteReceiver Web Management Interface, published on 4 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-28772 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-28772/ (Markdown: https://insights.sbomify.com/CVE-2026-28772/index.md)
```

## Sources

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

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