dbcve.org
GlpiApplication · Glpi Project

CVE-2024-37149

HIGH · 8.8 CVSS v3.1 Published 2024-07-10
Fix available
A fix is available. Upgrade to 10.0.16 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 an open-source asset and IT management software package that provides ITIL Service Desk features, licenses tracking and software auditing. An authenticated technician user can upload a malicious PHP script and hijack the plugin loader to execute this malicious script. 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

An authenticated technician user can upload a malicious PHP script and hijack the plugin loader to execute arbitrary PHP code, achieving remote code execution. The vulnerability stems from insufficient validation during plugin installation that allows bypassing the intended loader behavior.

MitigationUpgrade GLPI to version 10.0.16 or later to patch the insecure plugin loader handling. Restrict technician-level user permissions until the upgrade is applied.

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.85, < 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
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. Check installed GLPI version
    Locate the GLPI version file (typically version.php or config table in database) and read the installed version number. In GLPI, you can often find this in the file 'inc/commonitilobject.class.php' or by querying the database: SELECT value FROM glpi_configs WHERE name = 'version';
    Affected if The installed version is greater than or equal to 0.85 AND less than 10.0.16 (e.g., 10.0.15, 10.0.14, 9.5.x, etc.)
  2. Verify plugin module is enabled
    Check if the GLPI plugin system is active. Look in the database table glpi_plugins or check the /plugins directory exists and contains plugin files. Also check glpi_configs for 'plugins' setting.
    Affected if The plugin system is enabled and plugins directory contains installed plugins (indicates the vulnerable attack surface exists)
  3. Identify technician-level user accounts
    Query the database for users with technician profiles: SELECT name FROM glpi_users WHERE profiles_id IN (SELECT id FROM glpi_profiles WHERE name LIKE '%Technician%'); Or check user profile assignments in admin interface.
    Affected if There are active user accounts with Technician-level permissions - these users have the privileges needed to trigger the plugin upload vulnerability
  4. Inspect plugin upload directories
    Examine the /files/_plugins or /plugins directory for recently added PHP files. Look for unfamiliar plugins with suspicious filenames or timestamps. Check /files/_uploads if any exist and contain unexpected PHP files.
    Affected if Unexpected PHP files exist in plugin directories, or there are plugins with recent installation dates that you did not authorize
  5. Review plugin installation logs
    Check GLPI logs in /files/_logs/ or the database table glpi_logs for entries containing 'plugin' and 'install' or 'upload' around the time of suspicious activity. Look for entries indicating plugin was installed by a technician-level user.
    Affected if Logs show plugin installation activity performed by a user with technician-level permissions, indicating the vulnerable workflow was exercised

You are affected if your GLPI version is 0.85 or higher but below 10.0.16 AND the plugin system is enabled AND technician-level users exist in your system.

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 patch the insecure plugin loader handling. Restrict technician-level user permissions until the upgrade is applied.

Recommended fix High confidence

10.0.16

  1. 1. Create a complete backup of the GLPI database and all files, including configuration files
  2. 2. Download GLPI version 10.0.16 from the official GitHub repository or glpi-project.org
  3. 3. Extract the new version files
  4. 4. Replace the existing GLPI files with the new version files, preserving the config/config_db.php file
  5. 5. Clear the GLPI cache by deleting contents of the files/cache/ and files/tmp/ directories
  6. 6. Run the migration script by accessing the GLPI URL in a browser
  7. 7. Verify the installation by logging in and checking that plugins load correctly
Caveat Upgrading from older versions may require reviewing plugin compatibility and testing in a non-production environment first

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
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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