CVE-2025-48701
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 · uneditedopenDCIM through 23.04 allows SQL injection in people_depts.php because prepared statements are not used.
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 · moderate confidenceopenDCIM through version 23.04 contains a SQL injection vulnerability in people_depts.php. The application fails to use prepared statements when constructing database queries, allowing an attacker to inject malicious SQL code through user-supplied input. This could enable unauthorized data access or manipulation of the database.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Locate openDCIM installation and determine versionSearch the web server document root for the openDCIM application directory. Check for a version file (such as version.php, VERSION, or similar) in the root or docs folder. If no version file exists, check the application about page or the database configuration for version metadata. Common paths include /var/www/html/opendcim, /www/html/opendcim, or C:\inetpub\wwwroot\opendcim.Affected if The installed version is 23.04 or any earlier version of openDCIM
-
Confirm people_depts.php exists in web-accessible locationLocate the people_depts.php file within the openDCIM installation directory, typically found in the root or a subdirectory of the web-accessible application folder.Affected if The file exists in a web-accessible directory within the openDCIM installation
-
Inspect people_depts.php source code for direct SQL query constructionOpen people_depts.php in a text editor and search for SQL query patterns. Look for instances where database queries are built using string concatenation or string interpolation with user-supplied input (such as $_GET, $_POST, or directly accessed request parameters) rather than using prepared statements or parameter binding.Affected if The code contains SQL queries that incorporate user input through string concatenation or interpolation without using parameterized queries
-
Verify application has network exposure to untrusted usersDetermine whether the web server hosting openDCIM is accessible from untrusted networks (such as the public internet) or only from trusted internal networks. Check firewall rules, network ACLs, and web server configuration for the openDCIM vhost or directory.Affected if The application is accessible from untrusted networks and the vulnerable file is present
The environment is affected if running openDCIM version 23.04 or earlier and the people_depts.php file uses direct string concatenation to build SQL queries with user input.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataReplace all dynamic SQL queries in people_depts.php with parameterized queries (prepared statements). Apply input validation and output encoding as defense-in-depth. Update to the latest patched version when available.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48701 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-48701 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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