dbcve.org
GlpiApplication · Glpi Project

CVE-2023-35939

HIGH · 8.1 CVSS v3.1 Published 2023-07-05
Fix available
A fix is available. Upgrade to 10.0.8 or later.
See remediation →
87/100
Remediation priority · High
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. Starting in version 9.5.0 and prior to version 10.0.8, an incorrect rights check on a on a file accessible by an authenticated user (or not for certain actions), allows a threat actor to interact, modify, or see Dashboard data. Version 10.0.8 contains 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.5.0 through 10.0.7 contain an incorrect access control check on a file accessible by authenticated users (or unauthenticated users for certain actions), allowing threat actors to bypass authorization and interact with, modify, or view Dashboard data.

MitigationUpgrade GLPI to version 10.0.8 or later to apply the patch for the incorrect rights check 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:>= 9.5.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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Determine installed GLPI version
    Access the GLPI login page and view the footer, or check the version.php file in the GLPI root directory (e.g., /var/www/glpi/version.php)
    Affected if The installed version is 9.5.0 through 10.0.7 (any version >= 9.5.0 and < 10.0.8)
  2. Verify Dashboard feature is accessible
    Log into GLPI as an authenticated user and navigate to the Dashboard section (typically found in Setup > Dashboard or the main Dashboard view)
    Affected if Dashboard functionality is enabled and accessible to authenticated users
  3. Check for unauthenticated access to Dashboard
    Attempt to access Dashboard-related endpoints without logging in (e.g., direct URL paths like /front/dashboard.php or similar)
    Affected if Unauthenticated users can reach Dashboard components or API endpoints
  4. Inspect user authorization for Dashboard actions
    Create a low-privilege user account with minimal rights and test whether that account can view, modify, or delete Dashboard widgets or configurations that should be restricted
    Affected if Users with limited permissions can perform administrative Dashboard actions they should not be authorized to perform

The environment is affected if GLPI version is 9.5.0 through 10.0.7 AND the Dashboard feature is accessible to users who should not have full authorization to modify or view Dashboard 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 10.0.8 or later
Fixed in 10.0.8
Interim mitigation

Upgrade GLPI to version 10.0.8 or later to apply the patch for the incorrect rights check vulnerability.

Recommended fix High confidence

10.0.8

  1. 1. Backup your current GLPI installation and database before upgrading.
  2. 2. Download GLPI version 10.0.8 from the official GitHub repository or glpi-project.org.
  3. 3. Replace the existing GLPI files with the new version 10.0.8 files, preserving the config directory (/config) and the files directory (/files).
  4. 4. Run the upgrade process by accessing the GLPI URL in a web browser and following the on-screen prompts.
  5. 5. Verify that the upgrade completed successfully by logging in and checking the Dashboard functionality.
  6. 6. Confirm that the version displayed in GLPI is 10.0.8.
Caveat Review the GLPI 10.0.8 release notes for any breaking changes or migration requirements before upgrading

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

Fix this in Glpi Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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