dbcve.org
GlpiApplication · Glpi Project

CVE-2023-42461

CRITICAL · 9.8 CVSS v3.1 Published 2023-09-27
Fix available
A fix is available. Upgrade to 10.0.10 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 stands for Gestionnaire Libre de Parc Informatique is a Free Asset and IT Management Software package, that provides ITIL Service Desk features, licenses tracking and software auditing. The ITIL actors input field from the Ticket form can be used to perform a SQL injection. Users are advised to upgrade to version 10.0.10. There are no known workarounds for this vulnerability.

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.10 contain an authenticated SQL injection vulnerability in the ITIL actors input field of the Ticket form. An attacker with valid user credentials could inject malicious SQL queries through this input to manipulate the database, potentially extracting sensitive data, modifying records, or gaining further system access.

MitigationUpgrade GLPI to version 10.0.10 or later. There are no available workarounds; the upgrade is mandatory to remediate this critical vulnerability.

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, < 10.0.10

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 installed GLPI version
    Locate the version file (e.g., version.php or install/install.php) in the GLPI web root, or access the GLPI general setup page which displays the current version number.
    Affected if The installed version is 10.0.0 through 10.0.9 (any version >= 10.0.0 but < 10.0.10)
  2. Confirm Ticket module is active
    Log into GLPI with valid credentials and navigate to the main navigation menu. Look for the 'Assistance' or 'Tickets' menu item in the sidebar.
    Affected if The Tickets module is visible and accessible to your user account
  3. Verify ITIL actors field exists in Ticket form
    Create a new ticket or edit an existing ticket. Locate the 'Actors' or 'ITIL Actors' section in the ticket creation/editing form.
    Affected if The ITIL actors input field is present and editable in the Ticket form
  4. Check user has ticket creation or modification rights
    Go to Administration > Profiles > Your Profile. Verify that 'Ticket' create or update permissions are enabled for your user role.
    Affected if Your user account has permission to create or modify tickets with the actors field

You are affected if your GLPI version is 10.0.0 through 10.0.9 AND your user account has access to the Ticket module with the ITIL actors input field.

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.10 or later
Fixed in 10.0.10
Interim mitigation

Upgrade GLPI to version 10.0.10 or later. There are no available workarounds; the upgrade is mandatory to remediate this critical vulnerability.

Recommended fix High confidence

10.0.10

  1. 1. Create a complete backup of the GLPI database and all application files before proceeding
  2. 2. Download GLPI version 10.0.10 from the official source (github.com/glpi-project/glpi/releases or the official GLPI website)
  3. 3. Place the application in maintenance mode or ensure no users are accessing it during the upgrade
  4. 4. Extract the downloaded version 10.0.10 archive
  5. 5. Replace the existing GLPI files with the new version 10.0.10 files, preserving any custom configurations if required
  6. 6. Navigate to the GLPI directory in a web browser to trigger the database upgrade if prompted
  7. 7. Verify the upgrade was successful by logging in and checking the GLPI version number
  8. 8. Test that the Ticket form with ITIL actors input field functions correctly
Caveat Minor version upgrades typically have minimal breaking changes, but always review the changelog for any configuration or feature changes before upgrading production systems

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

Fix this in Glpi Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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