dbcve.org
GlpiApplication · Teclib Edition

CVE-2026-25936

HIGH · 8.8 CVSS v3.1 Published 2026-03-17
Fix available
A fix is available. Upgrade to after 11.0.6 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 11.0.0 and prior to version 11.0.6, an authenticated user can perfom a SQL injection. Version 11.0.6 fixes the 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 · moderate confidence

SQL injection vulnerability in GLPI versions 11.0.0 through 11.0.5 allows authenticated users to inject malicious SQL queries through unspecified input fields. The vulnerability is fixed in version 11.0.6.

MitigationUpgrade GLPI to version 11.0.6 or later. Until upgrade is completed, limit access to trusted authenticated users only and monitor for suspicious query patterns in logs.

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:> 11.0.0, <= 11.0.6

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 installed GLPI version
    Locate the GLPI version file (typically version.php in the root directory or config/Config.php) or check the database glpi_config table for the version field. Run: grep -r 'GLPI_VERSION' or query the database.
    Affected if The installed version is 11.0.1 through 11.0.6 (inclusive)
  2. Confirm user authentication is enabled
    Verify that the GLPI authentication system is active by checking the auth.* configuration tables or the setup/authentication settings in the admin panel. Check if the $CFG_GLPI['use_authentication'] setting is enabled in config/config.php or equivalent.
    Affected if Authentication is enabled and active in the GLPI installation
  3. Determine if any user accounts exist
    Query the glpi_users table in the database to list active user accounts: SELECT COUNT(*) FROM glpi_users WHERE is_active=1; Or check if user self-registration is permitted.
    Affected if There is at least one active user account in the system (any authenticated user can exploit this vulnerability)
  4. Check for SQL injection indicators in access logs
    Review web server access logs (Apache/nginx) and GLPI application logs for suspicious SQL syntax patterns in request parameters. Look for UNION SELECT, OR 1=1, DROP TABLE, or other SQL keywords in GET/POST parameters.
    Affected if SQL injection patterns are detected in HTTP requests to GLPI endpoints
  5. Inspect application input handling
    Examine the PHP source files in the /inc or /src directories for the affected component. Since the specific parameter is not identified in this CVE, search for dynamic SQL queries using $_GET, $_POST, or $_REQUEST without proper sanitization using prepare() or sql_escape().
    Affected if User-supplied input is used in SQL queries without parameterized statements or input validation

You are affected if your GLPI version is 11.0.1 through 11.0.6 and the application has at least one active authenticated user account.

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 a release after 11.0.6
Interim mitigation

Upgrade GLPI to version 11.0.6 or later. Until upgrade is completed, limit access to trusted authenticated users only and monitor for suspicious query patterns in logs.

Recommended fix High confidence

11.0.6

  1. 1. Back up the GLPI database and web files before upgrading
  2. 2. Download GLPI version 11.0.6 from the official source (github.com/glpi-project/glpi or get.glpi-project.org)
  3. 3. Extract the new version files to your web server document root
  4. 4. Run the GLPI update process by accessing the front controller (e.g., https://your-server/glpi/front/update.php)
  5. 5. Follow the on-screen upgrade wizard to complete the migration
  6. 6. Verify the application is functioning correctly after upgrade
  7. 7. Test that the SQL injection vulnerability is no longer exploitable
Caveat Review GLPI 11.0.6 release notes for any breaking changes or deprecations before upgrading in production

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-2026-25936 — 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-2026-25936 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