dbcve.org
GlpiApplication · Glpi Project

CVE-2024-47760

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.1.0 and prior to version 10.0.17, a technician with an access to the API can take control of an account with higher 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

A privilege escalation vulnerability in GLPI versions 9.1.0 through 10.0.16 allows a technician with API access to take control of higher-privilege accounts. The vulnerability is fixed in version 10.0.17.

MitigationUpgrade GLPI to version 10.0.17 or later to remediate 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.1.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 version
    Check the GLPI version displayed in the login page footer, or look for a version file in the GLPI installation directory (such as version.txt or in the /inc directory), or query the database for the version setting.
    Affected if The installed version is 9.1.0 through 10.0.16 (any version >= 9.1.0 and < 10.0.17)
  2. Verify API access is enabled
    Navigate to GLPI Administration > Setup > API (or Settings > API in older versions) and check if the API feature is enabled. Alternatively, check the configuration file inc/config.php or look for api keys in the glpi table glpi_configs.
    Affected if The API feature is enabled in the GLPI instance
  3. Identify technician accounts with API access
    Check user profiles in Administration > Users by reviewing which users have the API profile or profile token enabled. Look for users with Technician profile that have API credentials or tokens configured.
    Affected if There exists any user account with Technician (or higher) profile that has API access enabled (API token or API key configured)
  4. Check for unexpected privilege escalation indicators
    Review the GLPI audit logs or activity logs for any suspicious API calls that may have performed actions outside the expected scope of the technician account, such as password changes on admin or super-admin accounts.
    Affected if Unusual API activity or privilege escalation attempts are found in logs involving technician-level accounts

You are affected if GLPI version is 9.1.0 through 10.0.16 AND the API feature is enabled AND there are technician-level accounts with API access configured in your environment.

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 to remediate this privilege escalation vulnerability.

Recommended fix High confidence

10.0.17

  1. 1. Create a complete backup of the GLPI database and files
  2. 2. Download GLPI version 10.0.17 from the official GitHub repository or glpi-project.org
  3. 3. Extract the new version files to your web server document root
  4. 4. Copy the existing config/local_define.php file from the old installation to the new one
  5. 5. Ensure file permissions are correctly set (www-data or equivalent read/write)
  6. 6. Run the GLPI upgrade by accessing the application URL - the upgrade wizard should automatically start
  7. 7. Follow the on-screen prompts to complete the database upgrade
  8. 8. Verify the installation by logging in and checking that all plugins are functional
Caveat Review plugin compatibility with version 10.0.17 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
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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