dbcve.org
OpendcimApplication

CVE-2026-28517

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-27
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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 · unedited
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.

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 confidence

openDCIM versions 23.04 through commit 4467e9c4 contain an OS command injection vulnerability in report_network_map.php. The application retrieves the 'dot' configuration parameter from the database (fac_Config.dot) and passes it directly to the PHP exec() function without any validation or sanitization. An attacker who can modify the fac_Config.dot database value can execute arbitrary operating system commands in the context of the web server process.

MitigationSanitize and validate the 'dot' configuration parameter before passing it to exec(), or replace exec() with a safer alternative that does not allow command injection (such as using graphviz libraries programmatically rather than shell execution). Implement strict input validation to ensure only safe, expected values are accepted.

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 data
OpendcimApplication
Affected:= 23.04

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the vulnerable PHP file
    Search the web server document root for report_network_map.php (typically in the openDCIM web directory)
    Affected if The file exists and is accessible via the web server
  2. Verify openDCIM version
    Check the installed version of openDCIM by reviewing version files, composer.json, or the administrative interface
    Affected if Version is 23.04 exactly
  3. Inspect the vulnerable code pattern
    Open report_network_map.php and search for calls to exec() that use the 'dot' configuration parameter without validation (look for exec() calls referencing $fac_Config['dot'] or similar)
    Affected if The code passes the 'dot' parameter directly to exec() without sanitization
  4. Check database configuration access
    Examine the database for the fac_Config table and verify if the 'dot' value can be modified (check database user permissions or review the configuration write mechanism)
    Affected if The 'dot' value in fac_Config can be modified by an attacker
  5. Review current 'dot' configuration value
    Query the fac_Config table in the database for the 'dot' parameter value
    Affected if The 'dot' value contains unexpected content or has been altered from any documented default

The environment is affected if openDCIM 23.04 is installed, report_network_map.php exists with the exec() vulnerability, AND an attacker can modify the 'dot' configuration value in the fac_Config database table.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Sanitize and validate the 'dot' configuration parameter before passing it to exec(), or replace exec() with a safer alternative that does not allow command injection (such as using graphviz libraries programmatically rather than shell execution). Implement strict input validation to ensure only safe, expected values are accepted.

Recommended fix Moderate confidence

A version newer than 23.04 that includes the PR #1664 fix

  1. Review the changes in PR #1664 at https://github.com/opendcim/openDCIM/pull/1664 to understand the fix applied to report_network_map.php
  2. Apply the code changes from the pull request to sanitize/validate the 'dot' configuration parameter before passing it to exec()
  3. Alternatively, upgrade to a version of openDCIM newer than 23.04 that incorporates this security fix
  4. After applying the patch or upgrade, verify that the fac_Config.dot value is properly validated and cannot contain malicious commands

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Opendcim Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28517 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-28517 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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