CVE-2026-28516
Received Received - Intake
SQL Injection in openDCIM Config::UpdateParameter Allows Data Manipulation

Publication date: 2026-02-27

Last updated on: 2026-03-10

Assigner: VulnCheck

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 Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-27
Last Modified
2026-03-10
Generated
2026-05-07
AI Q&A
2026-02-28
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
opendcim opendcim 23.04
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The vulnerability in openDCIM version 23.04 is a SQL injection issue found in the Config::UpdateParameter function. Specifically, the install.php and container-install.php handlers take user-supplied input and insert it directly into SQL statements using string interpolation without using prepared statements or properly sanitizing the input. This flaw allows an authenticated user to execute arbitrary SQL commands on the underlying database.


How can this vulnerability impact me? :

This vulnerability can have severe impacts because it allows an authenticated user to run arbitrary SQL statements on the database. This could lead to unauthorized data access, data modification, or deletion, potentially compromising the integrity and confidentiality of the data managed by openDCIM.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

I don't know


What immediate steps should I take to mitigate this vulnerability?

I don't know


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart