dbcve.org
GlpiApplication · Glpi Project

CVE-2023-34107

MEDIUM · 6.5 CVSS v3.1 Published 2023-07-05
Fix available
A fix is available. Upgrade to 10.0.8 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 of the software starting with 9.2.0 and prior to 10.0.8 have an incorrect rights check on a on a file accessible by an authenticated user, allows access to the view all KnowbaseItems. Version 10.0.8 has a patch for this issue.

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 9.2.0 through 10.0.7 contain a broken access control vulnerability where an incorrect rights check on an endpoint allows any authenticated user to view all KnowbaseItems regardless of their actual permissions. This is an authorization bypass via insecure direct object reference.

MitigationUpgrade GLPI to version 10.0.8 or later which contains the patch for this incorrect rights check.

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:>= 9.2.0, < 10.0.8

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. Check installed GLPI version
    Locate the version.php file in the GLPI root directory (e.g., /var/www/glpi/version.php or similar path based on your installation). Open it and find the $CFG_GLPI['version'] or 'version' variable to read the exact version number.
    Affected if Version is 9.2.0 through 10.0.7 (any version >= 9.2.0 and < 10.0.8)
  2. Verify Knowbase module is enabled
    Log into GLPI as an administrator, navigate to Setup > Plugins (or Modules in some versions), and confirm whether the Knowbase (Knowledge Base) module is installed and enabled.
    Affected if Knowbase module is enabled and active in the GLPI instance
  3. Identify user access profile settings
    Go to Administration > Profiles in GLPI. For each profile, examine the Knowbase (or Knowledge Base) permissions: check whether Read (or View) rights are granted or denied for standard user profiles versus administrator profiles.
    Affected if Different profiles have varying Knowbase permissions, and the vulnerability allows bypass of these restrictions
  4. Test authorization bypass with low-privilege account
    Create or use a standard (non-admin) user account with limited or no Knowbase permissions. Authenticate with this account, then attempt to access the KnowbaseItem API endpoint directly (typically /front/knowbaseitem.php or /api/knowbaseitems/) or try to directly access a KnowbaseItem URL that should be restricted based on profile rights.
    Affected if A user without Knowbase read permissions can successfully view KnowbaseItem content that should be denied to their profile

If the GLPI version falls between 9.2.0 and 10.0.7 inclusive AND the Knowbase module is enabled, the environment is vulnerable to unauthorized access of KnowbaseItems regardless of user profile permissions.

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.8 or later
Fixed in 10.0.8
Interim mitigation

Upgrade GLPI to version 10.0.8 or later which contains the patch for this incorrect rights check.

Recommended fix High confidence

10.0.8

  1. 1. Back up your current GLPI installation and database before upgrading.
  2. 2. Download GLPI version 10.0.8 from the official GitHub repository or the GLPI website.
  3. 3. Extract the new version files to your web server document root.
  4. 4. Run the GLPI upgrade process by accessing the application in your browser or via command line.
  5. 5. Verify that the upgrade completed successfully and test that KnowbaseItem access controls are working correctly.

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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