dbcve.org
GlpiApplication · Glpi Project

CVE-2024-37148

HIGH · 8.1 CVSS v3.1 Published 2024-07-10
Fix available
A fix is available. Upgrade to 10.0.16 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
GLPI is an open-source asset and IT management software package that provides ITIL Service Desk features, licenses tracking and software auditing. An authenticated user can exploit a SQL injection vulnerability in some AJAX scripts to alter another user account data and take control of it. Upgrade to 10.0.16.

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 confidence

SQL injection vulnerability in GLPI's AJAX scripts allows any authenticated user to inject malicious SQL queries, potentially altering another user's account data and achieving account takeover. The vulnerability is exploitable without elevated privileges.

MitigationUpgrade GLPI to version 10.0.16 or later to remediate the SQL injection vulnerability.

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
GlpiApplication
Affected:>= 0.84, < 10.0.16

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
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate GLPI installation
    Search web server document roots for GLPI directories (e.g., /var/www/html/glpi, /www/glpi) or look for the 'glpi' folder in typical web paths. Check the version.php file in the root GLPI directory for the version number.
    Affected if GLPI is found and version.php exists but shows a version below 10.0.16 or version cannot be determined
  2. Check GLPI version from login page
    Access the GLPI login page and inspect the footer text which typically displays the GLPI version number.
    Affected if Displayed version is >= 0.84 and < 10.0.16
  3. Verify version against CVE range
    Compare your installed GLPI version to the affected range: versions 0.84 through 10.0.15 (inclusive) are vulnerable. Versions below 0.84 or 10.0.16 and above are not affected.
    Affected if Installed version is 0.84 or higher but lower than 10.0.16
  4. Confirm AJAX endpoint accessibility
    Test if the GLPI AJAX endpoint is accessible by attempting to access a known AJAX script path (e.g., /ajax/ticket.php or /ajax/dropdown.php). Check web server access logs for requests to /ajax/ paths.
    Affected if AJAX scripts are reachable and the GLPI version falls within the vulnerable range

You are affected if GLPI is installed and the version is 0.84 or higher but lower than 10.0.16, as the SQL injection flaw exists in this version range.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.0.16 or later
Fixed in 10.0.16
Interim mitigation

Upgrade GLPI to version 10.0.16 or later to remediate the SQL injection vulnerability.

Recommended fix High confidence

10.0.16 or later (10.0.x stable branch)

  1. 1. Create a complete backup of the GLPI database and file system before proceeding
  2. 2. Verify the current installed version by checking the version file or GLPI interface
  3. 3. Download GLPI version 10.0.16 (or latest 10.0.x version after 10.0.16) from the official source at glpi-project.org
  4. 4. Extract the new version files, replacing the existing installation while preserving the config/ and files/ directories
  5. 5. Run the upgrade process by accessing GLPI through a web browser and following the upgrade wizard
  6. 6. Clear any application caches if applicable
  7. 7. Verify the upgrade was successful by checking the GLPI version in the interface
  8. 8. Test that authentication and user management functionality work correctly
Caveat Review the GLPI 10.0.16 release notes for any specific migration steps or configuration changes; minor version upgrades typically have minimal breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Glpi Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-37148 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-37148 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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