dbcve.org
GlpiApplication · Glpi Project

CVE-2023-23610

MEDIUM · 6.5 CVSS v3.1 Published 2023-01-26
Fix available
A fix is available. Upgrade to 9.5.12 / 10.0.6 or later.
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. Versions prior to 9.5.12 and 10.0.6 are vulnerable to Improper Privilege Management. Any user having access to the standard interface can export data of almost any GLPI item type, even those on which user is not allowed to access (including assets, tickets, users, ...). This issue is patched in 10.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

GLPI versions prior to 9.5.12 and 10.0.6 contain an Improper Privilege Management vulnerability allowing any authenticated user with standard interface access to export data from item types (assets, tickets, users, etc.) they are not authorized to access. The data export function fails to properly enforce access controls.

MitigationUpgrade GLPI to version 10.0.6 (or 9.5.12 for the 9.x branch) to remediate the improper privilege management in the data export functionality.

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.65, < 9.5.12>= 10.0.0, < 10.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 the installed GLPI version
    Locate the version.php file in the GLPI root directory and read the $CFG_GLPI['version'] or similar version constant. Alternatively, access the GLPI login page or footer which often displays the version number.
    Affected if The installed version is prior to 9.5.12 (for 9.x branches) or prior to 10.0.6 (for 10.x branches), or if the version falls between 0.65 and 9.5.11, or between 10.0.0 and 10.0.5.
  2. Verify if the data export functionality exists
    Check if the export feature is present by navigating to an asset, ticket, or user profile in GLPI and looking for export options (such as export buttons, download options, or CSV/PDF export links) in the standard user interface accessible to authenticated users.
    Affected if The export functionality is present and accessible in the standard interface.
  3. Confirm user access level to the export feature
    Log in as a standard authenticated user with minimal permissions (not an administrator) and attempt to access the data export feature on item types such as assets, tickets, or users that this user should not have permission to view or export.
    Affected if A standard authenticated user can access and use the data export function on item types they are not authorized to access, demonstrating the privilege management flaw.

You are affected if your GLPI installation version is 9.5.11 or earlier in the 9.x branch, or 10.0.5 or earlier in the 10.x branch, AND the data export functionality is accessible to standard authenticated users who should not have access to all exported data.

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 9.5.12 / 10.0.6 or later
Fixed in 9.5.1210.0.6
Interim mitigation

Upgrade GLPI to version 10.0.6 (or 9.5.12 for the 9.x branch) to remediate the improper privilege management in the data export functionality.

Recommended fix High confidence

GLPI 9.5.12 or GLPI 10.0.6 (depending on your current major version branch)

  1. Identify current GLPI version by checking the dashboard or version file
  2. Download GLPI 9.5.12 (if currently on 9.x branch) or GLPI 10.0.6 (if currently on 10.x branch) from the official source
  3. Create a full backup of the GLPI database and files before upgrading
  4. Follow the standard GLPI upgrade procedure: extract the new version files, preserve the config/local_php file, run the migration scripts via web interface or CLI
  5. Verify the upgrade was successful and test that the privilege management fix is working
Caveat Review GLPI release notes for any breaking changes between your current version and the target fixed version before upgrading

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

Fix this in Glpi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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