Black Friday60% off BLACKFRIDAY2026
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
critical·Product Based Web Vulnerabilities·Updated Nov 18, 2026

CVE-2026-28516 Scanner

CVE-2026-28516 Scanner - Remote Code Execution (RCE) vulnerability in openDCIM

Est. Time~10 seconds
Scan TypeGroup Scan
Targetsdomain, subdomain, ipv4
CostFree
3
Times Used
continuous scan runs
4.3k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
9.3
CVSScritical
Exploitable remotely over the internet · no authentication required.
Description

openDCIM version 23.04, through commit 4467e9c4, contains a SQL injection vulnerability in Config::UpdateParameter. The install.php and container-install.php handlers pass user-supplied input directly into SQL statements using string interpolation without prepared statements or proper input sanitation. An authenticated user can execute arbitrary SQL statements against the underlying database.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
openDCIMby openDCIM
0
Updated Nov 18, 2026View on NVD →
Detail

openDCIM is a widely-used application in data centers for managing equipment inventories, rack layouts, and network configurations. It is used by system administrators and IT professionals for tracking and arranging all physical assets and operations of data center infrastructure. This software supports a myriad of features such as automated data collection, graphical location management, and power consumption analysis. Mainly, it is utilized in medium to large data centers and server rooms all over the world. Users depend on openDCIM for its accuracy in representing their IT resources and optimizing space and power in server racks. Its open-source nature allows users to customize and extend capabilities to fit their specific needs.

The Remote Code Execution (RCE) vulnerability in openDCIM permits attackers to execute arbitrary commands on the server hosting the application. This vulnerability occurs due to inadequate input validation within the install.php script, particularly in the LDAP configuration handler. It allows for an SQL injection that can be further exploited to gain RCE via the graph command execution functionality. Exploiting this flaw does not require authentication, making it especially dangerous. Attackers can effectively leverage it to gain unauthorized and potentially harmful access to a vulnerable openDCIM instance. Without remediation, this vulnerability remains as a critical threat to any deployment using the affected versions.

The technical root of the vulnerability lies in openDCIM's handling of LDAP request parameters, which are inadequately sanitized and directly passed into SQL UPDATE commands. The lack of prepared statements results in a stacked-query injection, which permits the overwriting of configuration parameters like the Graphviz binary path. This, in turn, allows an attacker to inject system commands that are subsequently executed by the report_network_map.php script. Crucially, the exploit can fully compromise the system by assuming the privileges of the web server user on affected Docker deployments. The endpoints examined expose the application to serious exploits through improper input handling and execution sequences.

If exploited, this vulnerability may allow malicious actors to execute any arbitrary code on compromised systems, leading to data theft, infrastructure disruption, and potential server control. Attackers can manipulate system settings or infuse harmful software into the environment. The exploitation could result in unauthorized access to sensitive information or complete operational failure of the openDCIM-deployed infrastructure. Due to the sensitive nature of data centers, any breach could expose confidential data and result in significant financial and reputational damage to organizations. Hence, immediate attention to patching and safeguarding systems against such threats is paramount.

REFERENCES

Solution Advice
  • Upgrade openDCIM to the latest release that addresses this specific vulnerability.
  • Disable public access to install.php and ensure post-installation locks are applied.
  • Employ firewall rules to restrict access to critical resources until the patch is applied.
  • Regularly review configuration for unauthorized changes and redundant access permissions.
  • Implement Web Application Firewall (WAF) to filter malicious requests.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

12,000+ scanners. Free to start. No credit card required.