Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Critical · CVSS 9.3

How to Fix CVE-2026-28516: openDCIM (Bundle Sibling)

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-28516 is a sibling vulnerability in the same vendor advisory as CVE-2026-28515. Apply the same patched build and you close both. The technical detail below is what differs.

⚡ At a glance
Severity9.3 (Critical)
Actively exploited?No public listing in CISA KEV
AffectedopenDCIM 0 to <=23.04
Fixed inSame patched build as CVE-2026-28515
Type (CWE)CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

What's different about CVE-2026-28516?

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.

How to fix CVE-2026-28516

Apply the patched build per the primary write-up: How to Fix CVE-2026-28515. All commands, verification steps, and rollback notes for openDCIM are listed there.

Frequently asked questions

Does the CVE-2026-28515 patch close CVE-2026-28516?

Yes. Both CVEs are addressed by the same vendor patch. Applying the patched build closes the full bundle.

Is CVE-2026-28516 listed in CISA KEV?

No public KEV listing at the time of this writing.

Where is the official advisory?

See https://chocapikk.com/posts/2026/opendcim-sqli-to-rce/

References


*Written by Sai Kiran Pandrala. Part of the openDCIM bundle. Full procedure at how-to-fix-cve-2026-28515.*