dbcve.org
GlpiApplication · Glpi Project

CVE-2024-47758

HIGH · 8.8 CVSS v3.1 Published 2024-12-11
Fix available
A fix is available. Upgrade to 10.0.17 or later.
See remediation →
94/100
Remediation priority · Urgent
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 a free asset and IT management software package. Starting in version 9.3.0 and prior to version 10.0.17, an authenticated user can use the API to take control of any user that have the same or a lower level of privileges. Version 10.0.17 contains a patch for this issue.

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

An authenticated user can exploit the GLPI API to take control of any user with the same or lower privilege level, enabling privilege escalation within the application.

MitigationUpgrade GLPI to version 10.0.17 or later, which contains the patch for this privilege escalation 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:>= 9.3.0, < 10.0.17

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
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 checks

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

  1. Identify GLPI installation and version
    Locate the GLPI installation directory and check the version.php or VERSION file, typically found at glpi/inc/version.php or glpi/version in the web root. Alternatively, access the GLPI login page footer which often displays the version number.
    Affected if The installed version is >= 9.3.0 and < 10.0.17
  2. Confirm API access is enabled
    Check the GLPI configuration file (config_db.php or config/config.php) for API settings, or navigate to Setup > General > API in the GLPI web interface to verify that the REST API is enabled.
    Affected if The REST API is enabled and accessible (the vulnerability requires API access to exploit)
  3. Verify API tokens exist
    Check for active API tokens in the GLPI database table 'glpi_configs' (config_name = 'api_tokens' or 'glpi_session' related settings) or via the web interface under Setup > General > API > API Tokens, or by querying the API endpoint /apirest.php/initSession with valid credentials.
    Affected if There is at least one user with API token or credentials configured for API access

The environment is affected if GLPI version is 9.3.0 or higher but below 10.0.17 AND the REST API is enabled with at least one user having API access credentials.

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.17 or later
Fixed in 10.0.17
Interim mitigation

Upgrade GLPI to version 10.0.17 or later, which contains the patch for this privilege escalation vulnerability.

Recommended fix High confidence

10.0.17

  1. 1. Create a complete backup of the GLPI database and the web directory files before proceeding with any upgrade.
  2. 2. Confirm the current GLPI version by navigating to Setup > General > System information in the GLPI web interface or by checking the version file in the installation directory.
  3. 3. Download GLPI version 10.0.17 from the official GitHub repository at github.com/glpi-project/glpi or from the official GLPI website.
  4. 4. Extract the downloaded archive and replace the existing GLPI files, preserving the config/local_define.php file if it exists.
  5. 5. Run the upgrade process by accessing the GLPI web interface - the system should automatically detect the new version and prompt for database migration.
  6. 6. Follow the on-screen instructions to complete the database migration.
  7. 7. Clear any caching systems (like opcache) if applicable after the upgrade.
  8. 8. Verify the upgrade was successful by checking the GLPI version in Setup > General > System information - it should show 10.0.17.
Caveat Review the GLPI 10.0.17 release notes for any migration considerations or deprecation warnings before upgrading in production environments.

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

Fix this in Glpi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47758 — 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-47758 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