dbcve.org
GlpiApplication · Glpi Project

CVE-2023-37278

CRITICAL · 9.1 CVSS v3.1 Published 2023-07-13
Fix available
A fix is available. Upgrade to 10.0.9 or later.
See remediation →
97/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, Data center management, ITIL Service Desk, licenses tracking and software auditing. An administrator can trigger SQL injection via dashboards administration. This vulnerability has been patched in version 10.0.9.

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 before 10.0.9 contain an SQL injection vulnerability in the dashboards administration functionality. An authenticated administrator can inject malicious SQL queries through dashboard parameters, potentially allowing unauthorized data access, modification, or complete database compromise.

MitigationUpgrade GLPI to version 10.0.9 or later to patch the SQL injection vulnerability. If immediate patching is not possible, restrict administrative access and monitor dashboard-related database queries.

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

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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 or similar in the inc directory), or access the GLPI system information page via the web interface (Help > About, or /index.php?noAUTO=1). Compare the displayed version number against the affected range (all versions before 10.0.9).
    Affected if The installed version is below 10.0.9 (e.g., 10.0.8, 10.0.7, 10.0.6, etc.)
  2. Verify administrator access to dashboards
    Log in to GLPI with an administrator account and navigate to the dashboards administration section (typically found under Administration > Dashboards or similar path). Confirm whether the dashboard configuration interface is accessible and allows parameter modification.
    Affected if You have an authenticated administrator account that can access and modify dashboard parameters
  3. Check for dashboard-related file modifications
    If you have file system access, examine the dashboard-related PHP files in the GLPI installation (typically in the src/ or inc/ directories). Look for files handling dashboard parameters and check for any unexpected code patterns, particularly around SQL query construction.
    Affected if The dashboard parameter handling code appears modified or contains unsanitized variable usage in SQL queries
  4. Review database user privileges
    Examine the database user credentials configured in GLPI's config file (usually db.function.php or similar). Determine if the application database user has elevated privileges beyond what is required (e.g., DROP, GRANT, or FILE privileges).
    Affected if The GLPI database user has excessive privileges beyond SELECT, INSERT, UPDATE, and DELETE

Your environment is affected if GLPI version is below 10.0.9 AND an authenticated administrator can access the dashboard administration functionality to inject SQL through dashboard parameters.

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.9 or later
Fixed in 10.0.9
Interim mitigation

Upgrade GLPI to version 10.0.9 or later to patch the SQL injection vulnerability. If immediate patching is not possible, restrict administrative access and monitor dashboard-related database queries.

Recommended fix High confidence

GLPI 10.0.9

  1. 1. Back up your GLPI database and files before proceeding with the upgrade
  2. 2. Download GLPI version 10.0.9 from the official GitHub repository (github.com/glpi-project/glpi/releases) or the official GLPI website
  3. 3. Replace your existing GLPI installation files with the new version 10.0.9 files
  4. 4. Run the GLPI update process by accessing your GLPI URL and following the on-screen upgrade instructions
  5. 5. Verify that the upgrade completed successfully by logging into GLPI
  6. 6. Test that the dashboards administration functionality works correctly after the upgrade
  7. 7. Confirm that the SQL injection vulnerability is remediated by verifying no unauthorized database queries can be executed through the dashboards interface
Caveat Review the GLPI 10.0.9 release notes for any breaking changes or deprecations before upgrading in production environments

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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