dbcve.org
GlpiApplication · Glpi Project

CVE-2026-26263

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-06
Fix available
A fix is available. Upgrade to 11.0.6 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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. From 11.0.0 to before 11.0.6, an unauthenticated time-based blind SQL injection exists in GLPI's Search engine. This vulnerability is fixed in 11.0.6.

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

Unauthenticated time-based blind SQL injection vulnerability in GLPI's Search engine affecting versions 11.0.0 through 11.0.5. Attackers can exploit this critical (CVSS 9.8) flaw without credentials to inject malicious SQL queries via the search functionality.

MitigationUpgrade GLPI to version 11.0.6 or later to apply the vendor patch. If immediate upgrade is not feasible, consider restricting network access to the GLPI instance as a compensating control.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 file (typically version.php or similar version metadata file in the root GLPI directory). Common paths include /var/www/html/glpi/ or the web root where GLPI is installed.
    Affected if The installed version is 11.0.0, 11.0.1, 11.0.2, 11.0.3, 11.0.4, or 11.0.5
  2. Verify the Search engine is accessible
    Confirm that the GLPI web interface Search functionality is enabled and accessible without authentication. The vulnerability exists in the Search engine component.
    Affected if The Search feature is enabled and exposed (this is the default state in affected versions)
  3. Check web server access logs for SQL injection patterns
    Review web server access logs (Apache, Nginx, etc.) for requests to GLPI search endpoints containing SQL injection payloads such as time-based functions (SLEEP, BENCHMARK) or boolean-based indicators in search parameters.
    Affected if Log entries show suspicious search parameter patterns with SQL time-delay functions or unusual boolean conditions
  4. Examine database query logs for time-based injection signatures
    If database logging is enabled, review MySQL/PostgreSQL logs for unusually long-running queries or patterns indicative of time-based blind SQL injection (repeated SLEEP calls or heavy computational functions).
    Affected if Database logs show suspicious time-delay queries or unexpected SQL execution patterns originating from GLPI search operations

You are affected if GLPI version 11.0.0 through 11.0.5 is installed and the Search engine feature is accessible, as this is where the unauthenticated SQL injection vulnerability resides.

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 11.0.6 or later
Fixed in 11.0.6
Interim mitigation

Upgrade GLPI to version 11.0.6 or later to apply the vendor patch. If immediate upgrade is not feasible, consider restricting network access to the GLPI instance as a compensating control.

Recommended fix High confidence

11.0.6

  1. Create a complete backup of the GLPI database and all files
  2. Enable maintenance mode to prevent user access during upgrade
  3. Download GLPI version 11.0.6 from the official GLPI repository (github.com/glpi-project/glpi)
  4. Extract the new version files
  5. Replace the existing GLPI installation files with the new 11.0.6 files
  6. Run any database migration scripts if included (typically automatic on next access)
  7. Verify the installation by logging in and testing core functionality
  8. Disable maintenance mode
Caveat Standard upgrade precautions apply - backup before upgrading; review release notes for any migration requirements

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

Fix this in Glpi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
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,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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