VulnerabilityPublished 25 Dec 2025Updated 26 Dec 2025

CVE-2025-15081: JD Cloud BE6500 · Command Injection

Affects JD Cloud BE6500Source CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 2.5% chance of exploitation in 30 days – higher than 84% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

These include restricting network access to the /jdcapi endpoint using firewalls or network segmentation to limit exposure to trusted sources only. Employ strict input validation and filtering at the application or proxy level to detect and block malicious ddns_name parameter values. Monitor logs and network traffic for unusual command execution patterns or anomalies related to the vulnerable function. Deploy intrusion detection/prevention systems (IDS/IPS) with signatures targeting this specific exploit. Consider isolating or temporarily disabling vulnerable services if feasible until a vendor patch is released. Engage with JD Cloud support channels for updates and apply patches promptly once available. Additionally, conduct thorough security audits and penetration tests focusing on cloud infrastructure to identify any exploitation attempts.

Description

CVE-2025-15081 is a medium-severity command injection vulnerability found in JD Cloud BE6500 version 4.4.1.r4308. It affects the sub_4780 function in the /jdcapi component, where manipulation of the ddns_name argument allows remote attackers to execute arbitrary commands. The vulnerability requires no user interaction and no privileges beyond limited privileges, making it remotely exploitable over the network. Although the vendor was notified, no patch or response has been provided, and a public exploit disclosure exists. This vulnerability could lead to partial compromise of confidentiality, integrity, and availability of affected systems. European organizations using JD Cloud BE6500 should prioritize monitoring and containment measures due to the lack of vendor mitigation. Countries with higher adoption of JD Cloud infrastructure and critical cloud service dependencies are at greater risk.

Impact

For European organizations, the exploitation of CVE-2025-15081 could result in unauthorized command execution on critical cloud infrastructure, leading to data breaches, service disruption, or unauthorized access to sensitive resources. Given the cloud-centric nature of JD Cloud BE6500, organizations using this platform for hosting applications or data could face significant operational risks. The lack of vendor response and patch availability increases exposure time, elevating the likelihood of attacks. Compromise could affect confidentiality through data leakage, integrity via unauthorized modifications, and availability by disrupting cloud services. Organizations in sectors such as finance, telecommunications, and government, which often rely on cloud infrastructure, may experience heightened risk and potential regulatory implications under GDPR if personal data is exposed.

Summary

CVE-2025-15081 is a command injection vulnerability identified in JD Cloud BE6500 version 4.4.1.r4308, specifically within the sub_4780 function of the /jdcapi file. The vulnerability arises from improper sanitization of the ddns_name argument, which an attacker can manipulate to inject and execute arbitrary system commands remotely. The attack vector is network-based, requiring no user interaction and only limited privileges, which lowers the barrier for exploitation. The vulnerability impacts confidentiality, integrity, and availability by potentially allowing attackers to execute commands that could extract sensitive data, alter system configurations, or disrupt services. Despite early vendor notification, no patches or mitigations have been released, and a public exploit has been disclosed, increasing the risk of exploitation. The CVSS 4.0 score of 5.3 reflects a medium severity, considering the ease of exploitation and partial impact on system security. This vulnerability is particularly concerning for cloud environments relying on JD Cloud BE6500, as it could be leveraged for lateral movement or persistent access within compromised networks.

References

Community reviews

Loading reviews…