CVE-2026-7705
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 · uneditedA flaw has been found in JD Cloud JDCOS 4.5.1.r4518. This vulnerability affects the function set_iptv_info of the file /jdcap of the component Service Interface. Executing a manipulation of the argument vid can lead to command injection. It is possible to launch the attack remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 · moderate confidenceJD Cloud JDCOS 4.5.1.r4518 contains a command injection vulnerability in the set_iptv_info function within the /jdcap Service Interface. The vid argument is not properly sanitized before being used in a system command, allowing an attacker to inject arbitrary OS commands remotely.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 JD Cloud JDCOS installation and versionLocate JDCOS version file, check system info, or query the service API for its version response. Common locations include version configuration files or the /jdcap version endpoint.Affected if The installed version matches 4.5.1.r4518 or the version reporting indicates JDCOS without a patched version number.
-
Confirm /jdcap Service Interface is exposedVerify the /jdcap endpoint is accessible on the network. Check firewall rules, reverse proxy configurations, or service bindings to determine if this management interface is exposed.Affected if The /jdcap Service Interface is reachable from network locations where untrusted input could be submitted.
-
Locate set_iptv_info function configurationInspect the JDCOS service configuration files or API documentation to confirm the set_iptv_info function is registered and available within the /jdcap interface.Affected if The set_iptv_info function is present and enabled in the deployed service configuration.
-
Inspect vid parameter handling in set_iptv_infoExamine the source code, decompiled classes, or configuration for the set_iptv_info function to determine if the vid argument undergoes input validation or sanitization before being passed to system command execution.Affected if The vid parameter is used directly in a system call without sanitization, parameterization, or input validation checks.
You are affected if running JD Cloud JDCOS version 4.5.1.r4518 with the /jdcap Service Interface exposed and the set_iptv_info function using the vid parameter in system commands without input sanitization.
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 dataApply vendor patch when available; implement strict input validation and sanitization on the vid parameter before use in system calls; consider using parameterized APIs instead of shell commands.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7705 — 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-7705 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