CVE-2026-28778
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInternational Datacasting Corporation (IDC) SFX Series SuperFlex Satellite Receiver contains undocumented, hardcoded/insecure credentials for the `xd` user account. A remote unauthenticated attacker can log in via FTP using these credentials. Because the `xd` user has write permissions to their home directory where root-executed binaries and symlinks (such as those invoked by `xdstartstop`) are stored, the attacker can overwrite these files or manipulate symlinks to achieve arbitrary code execution as the root user.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe IDC SFX Series SuperFlex Satellite Receiver contains undocumented hardcoded FTP credentials for the `xd` user account. A remote unauthenticated attacker can leverage these credentials to access the device via FTP. Due to the `xd` user having write permissions to their home directory containing root-executed binaries and symlinks (including those invoked by `xdstartstop`), an attacker can overwrite these files or manipulate symlinks to achieve arbitrary code execution as the root user.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device model and firmware versionAccess the device management interface or use SNMP/SSH to query the system information. Look for model identifier 'Sfx2100' or 'Datacast SFX Series' and note the firmware version string.Affected if The device is a Datacast Sfx2100 with any firmware version.
-
Confirm FTP service is enabled and accessibleAttempt to connect to the device on TCP port 21 (FTP). Use a network scanner or manual FTP client connection to verify the FTP service is listening and accepts connections.Affected if FTP port 21 is open and the service accepts authentication attempts.
-
Test hardcoded xd user credentialsAttempt FTP login using username 'xd' with the documented hardcoded password (consult CVE-2026-28778 reference for the specific credential pair). Verify successful authentication.Affected if The 'xd' user authenticates successfully with the known hardcoded credentials.
-
Check xd user home directory contentsAfter FTP login as 'xd', list the contents of the home directory (typically /home/xd or /xd). Look for executable binaries, scripts, or symlinks that are owned by root or invoked with elevated privileges.Affected if The xd user's home directory contains root-owned executables or symlinks that can be overwritten or manipulated.
-
Verify write access to home directoryUsing the FTP session, attempt to upload a test file to the xd user's home directory to confirm write permissions.Affected if Write access is granted to the xd user's home directory via FTP.
If the device is a Datacast Sfx2100 with FTP enabled and the hardcoded xd user credentials allow FTP access with write permissions to a directory containing root-executed binaries, the environment is affected by CVE-2026-28778.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImmediately change or remove the hardcoded credentials for the `xd` account, disable FTP access if not required, and restrict network access to the management interface. Additionally, review and remediate file permissions on directories containing root-executed binaries to prevent symlink manipulation attacks.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28778 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-28778 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data