dbcve.org
GlpiApplication · Glpi Project

CVE-2024-47761

HIGH · 7.2 CVSS v3.1 Published 2024-12-11
Fix available
A fix is available. Upgrade to 10.0.17 or later.
See remediation →
78/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 a free asset and IT management software package. Starting in version 0.80 and prior to version 10.0.17, an administrator with access to the sent notifications contents 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

GLPI asset management software versions 0.80 through 10.0.16 contain a privilege escalation vulnerability where an administrator with access to sent notification contents can manipulate notifications to take control of higher-privileged accounts. This appears to be an injection or session hijack flaw in the notification handling system.

MitigationUpgrade GLPI to version 10.0.17 or later. Until patched, restrict administrative access to notification contents and monitor for unauthorized account modifications.

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.80, < 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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 installed GLPI version
    Locate the version file or access the GLPI administration panel to determine the running version. Common locations include a version.php file in the root directory or the System Info page in the admin dashboard.
    Affected if The installed version falls within the range 0.80 through 10.0.16 (any version before 10.0.17).
  2. Verify notification module status
    Access the GLPI administration panel and navigate to Setup > Notifications to determine if the notification system is enabled and configured.
    Affected if Notifications are enabled and administrators have access to view or edit notification contents.
  3. Review recent account modifications
    Check the GLPI audit logs or user history for any unexpected changes to user privileges, password resets, or role modifications, particularly on super-admin or admin accounts.
    Affected if There are unauthorized or unexpected account privilege changes that were not performed by known administrators.
  4. Inspect notification templates for tampering
    Examine the notification templates in the GLPI database or configuration files for any suspicious injection patterns, unexpected script tags, or malformed content that could indicate manipulation.
    Affected if Notification templates contain unexpected code, scripts, or modified content that was not intentionally added by the administrator.

The environment is affected if GLPI versions 0.80 through 10.0.16 are running with the notification system enabled, allowing administrators with notification access to potentially inject malicious content and escalate privileges.

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. Until patched, restrict administrative access to notification contents and monitor for unauthorized account modifications.

Recommended fix High confidence

10.0.17

  1. 1. Back up the current GLPI installation directory and database before proceeding with the upgrade
  2. 2. Download GLPI version 10.0.17 from the official GLPI repository (github.com/glpi-project/glpi)
  3. 3. Replace the existing GLPI files with the new version 10.0.17 files, preserving any local configuration and customizations
  4. 4. Run the GLPI upgrade process by accessing the application (usually by visiting the GLPI URL)
  5. 5. Verify the installation was successful and test that the application functions correctly
  6. 6. Confirm the vulnerability is resolved by verifying that the authentication mechanism properly handles notification contents

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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