CVE-2024-45608
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 · uneditedGLPI is a free asset and IT management software package. An authenticated user can perfom a SQL injection by changing its preferences. Upgrade to 10.0.17.
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 confidenceGLPI versions before 10.0.17 contain a SQL injection vulnerability in the user preferences functionality. An authenticated user can inject malicious SQL queries through preference parameters, potentially allowing unauthorized data access, manipulation, or privilege escalation within the database.
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>= 9.5.0, < 10.0.17CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify GLPI installation locationLocate GLPI by searching for typical web application directories or checking your web server document roots for a 'glpi' folder containing the standard GLPI file structure (index.php, install.php, etc.)Affected if GLPI software is present on the system
-
Determine installed GLPI versionCheck the version file or file header within the GLPI directory. Common methods include: looking for a version.php file in the 'inc' or 'src' folder, checking the footer in the web interface, or running a grep command for version-related strings in the codebaseAffected if The installed version is 9.5.0 or higher but lower than 10.0.17
-
Verify user authentication is enabledCheck if GLPI's user authentication system is active by confirming that user login functionality is working and users can authenticate to the platformAffected if User authentication is enabled and user accounts exist in the system
-
Confirm user preferences functionality is accessibleAccess the user preferences/settings area within GLPI by logging in as an authenticated user and navigating to the preferences or personal settings section of the interfaceAffected if The user preferences feature is accessible to authenticated users
-
Check for signs of SQL injection exploitationReview database logs or application logs for unusual SQL queries originating from user preference update actions, look for unexpected data access patterns, or examine the database for unauthorized recordsAffected if Suspicious SQL patterns appear in logs or unauthorized database queries are detected
A system is affected if GLPI versions 9.5.0 through 10.0.16 are installed with user authentication enabled and the preferences feature is accessible to authenticated users.
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.
dbcve · scoped10.0.17
Upgrade GLPI to version 10.0.17 or later to remediate this SQL injection vulnerability. If immediate patching is not feasible, restrict access to the GLPI application to trusted users only until the upgrade can be completed.
10.0.17
- Create a complete backup of the GLPI database and all files
- Download GLPI version 10.0.17 from the official GitHub releases or glpi-project.org
- Extract the new version files to a temporary location
- Replace the existing GLPI files with the new version files, preserving the config/local_define.php file
- Ensure file permissions are correctly set (typically apache/www-data ownership)
- Access the GLPI web interface and complete any database migration prompts if presented
- Verify the installation by logging in and checking that preferences can be changed without SQL errors
- Confirm the GLPI version shows 10.0.17 in the system information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.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,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45608 — 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-2024-45608 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