dbcve.org
GlpiApplication · Glpi Project

CVE-2022-29250

MEDIUM · 6.5 CVSS v3.1 Published 2022-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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, that provides ITIL Service Desk features, licenses tracking and software auditing. In versions prior to version 10.0.1 it is possible to add extra information by SQL injection on search pages. In order to exploit this vulnerability a user must be logged in.

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 versions prior to 10.0.1 contain an SQL injection vulnerability in the search functionality that allows authenticated users to inject malicious SQL statements through search page parameters, potentially allowing unauthorized data access or manipulation of the database.

MitigationUpgrade GLPI to version 10.0.1 or later to remediate this SQL injection vulnerability. As a defense-in-depth measure, restrict search page access to only necessary authenticated users and monitor database query logs for anomalous patterns.

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:= 10.0.0

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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 directory
    Locate the GLPI web application directory on the server (commonly in /var/www/html/glpi, /www/glpi, or similar web root paths)
    Affected if The GLPI application is present on the system
  2. Check installed GLPI version
    Look for a version file or configuration within the GLPI directory. Common locations include a version.php file, composer.json, or the config GLPI_VERSION constant. Compare the found version to 10.0.0
    Affected if The installed version is exactly 10.0.0 (earlier versions may also be vulnerable but this CVE specifically targets 10.0.0)
  3. Verify authenticated access to search functionality
    Confirm that the GLPI search page (typically /front/search.php) is accessible to authenticated users with standard user accounts, not restricted to admin-only
    Affected if Authenticated non-admin users can access the search functionality, which is the default configuration
  4. Check for anomalous database query patterns
    Review database query logs (MySQL/PostgreSQL general query log, slow query log, or audit logs) for suspicious SQL syntax within search-related SELECT statements, especially where search parameters might be logged
    Affected if Unexpected SQL syntax or UNION-based queries appear in database logs originating from GLPI search requests

You are affected if GLPI version 10.0.0 is installed and the search functionality is accessible to authenticated users (the default configuration).

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade GLPI to version 10.0.1 or later to remediate this SQL injection vulnerability. As a defense-in-depth measure, restrict search page access to only necessary authenticated users and monitor database query logs for anomalous patterns.

Recommended fix High confidence

10.0.1

  1. Download GLPI version 10.0.1 from the official GLPI project repository or website
  2. Create a complete backup of the GLPI database and all files
  3. Place the site in maintenance mode or ensure no users are accessing during upgrade
  4. Extract the new version files, overwriting the existing installation
  5. Run the GLPI upgrade process by accessing the application in a web browser
  6. Follow any on-screen upgrade prompts to complete the database migration
  7. Verify the upgrade was successful by logging in and checking the GLPI version
  8. Disable maintenance mode once upgrade is confirmed
Caveat Minor version upgrade typically has minimal breaking changes; review release notes for any configuration changes

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
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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