dbcve.org
GlpiApplication · Glpi Project

CVE-2026-22044

HIGH · 8.8 CVSS v3.1 Published 2026-02-04
Fix available
A fix is available. Upgrade to 10.0.23 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. From version 0.85 to before 10.0.23, an authenticated user can perform a SQL injection. This issue has been patched in version 10.0.23.

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

GLPI versions 0.85 through 10.0.22 contain an authenticated SQL injection vulnerability that allows an authenticated user to inject arbitrary SQL commands through unspecified input vectors. This could allow data exfiltration, modification, or potential command execution depending on database privileges.

MitigationUpgrade GLPI to version 10.0.23 or later to patch the SQL injection vulnerability. If immediate patching is not possible, restrict administrative access and monitor database queries for suspicious activity.

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.23

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 installation
    Locate GLPI by searching for common paths such as /var/www/html/glpi, /opt/glpi, or check your web server document root for glpi directories. Alternatively, search for files named glpi or config_db.php using: find / -name 'config_db.php' 2>/dev/null
    Affected if GLPI software is present on the system
  2. Determine installed GLPI version
    Check the version file typically located at VERSION or version.php in the GLPI root directory, or access /marketplace/glpi/scripts/verify_release_version if those directories exist. You can also check the footer of the GLPI login page which often displays the version number.
    Affected if The installed version is 0.85 through 10.0.22 inclusive (any version >= 0.85 but < 10.0.23)
  3. Verify authentication is enabled
    Confirm that the GLPI web interface allows user authentication. Try accessing the login page and verify that local user accounts, LDAP integration, or SSO authentication is configured and active.
    Affected if User authentication is enabled and user accounts exist in the system
  4. Check database user privileges
    Review the database credentials in config_db.php to determine what privileges the GLPI database user has. SQL injection impact is higher if the database user has privileges beyond SELECT, such as INSERT, UPDATE, or administrative rights.
    Affected if The database user has elevated privileges (not restricted to read-only)
  5. Review database query logs
    Enable and review MySQL/PostgreSQL query logging. Search logs for unusual or suspicious SQL commands, especially those containing UNION SELECT, DROP, or other SQL keywords originating from GLPI application sessions.
    Affected if Unusual or malicious SQL queries are found in database logs

Your environment is affected if GLPI is installed with a version between 0.85 and 10.0.22 and user authentication is enabled, regardless of whether the specific injection vector is known.

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.23 or later
Fixed in 10.0.23
Interim mitigation

Upgrade GLPI to version 10.0.23 or later to patch the SQL injection vulnerability. If immediate patching is not possible, restrict administrative access and monitor database queries for suspicious activity.

Recommended fix High confidence

10.0.23

  1. 1. Backup your GLPI database and all files before starting the upgrade.
  2. 2. Download GLPI version 10.0.23 from the official GitHub repository (github.com/glpi-project/glpi) or the official website.
  3. 3. Put GLPI in maintenance mode if possible to prevent user access during upgrade.
  4. 4. Replace all existing GLPI files with the new version 10.0.23 files, preserving any custom configuration files (like config_db.php).
  5. 5. Navigate to the GLPI web URL to trigger the database migration process if required.
  6. 6. Clear any application caches if applicable.
  7. 7. Verify the upgrade was successful by logging in and checking the version number.
  8. 8. Test critical functionality to ensure the upgrade did not break existing features.
Caveat Minor point release upgrade; review release notes for any minor compatibility notes

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-22044 — 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-22044 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