CVE-2026-28516: Opendcim SQL injection (CVSS 8.8)

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.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredLow

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

Opendcim23.04

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

Patch & vendor advisories

References

https://chocapikk.com/posts/2026/opendcim-sqli-to-rce/ExploitThird Party Advisory
https://github.com/Chocapikk/opendcim-exploitExploit
https://github.com/opendcim/openDCIM/blob/4467e9c4/config.inc.php#L75-L90Product
https://github.com/opendcim/openDCIM/blob/4467e9c4/install.php#L420-L434Product
https://github.com/opendcim/openDCIM/pull/1664Issue TrackingPatch
https://github.com/opendcim/openDCIM/pull/1664/changes/8f7ab2a710086a9c8c269560793e47c577ddda09Issue TrackingPatch
https://www.vulncheck.com/advisories/opendcim-sql-injection-in-config-updateparameterThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-28516 being actively exploited?

CVE-2026-28516 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 1.54%.

How severe is CVE-2026-28516?

CVE-2026-28516 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 1.54% probability of exploitation.

Which products are affected by CVE-2026-28516?

Affected products include Opendcim.

How do I fix CVE-2026-28516?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-28516 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo