dbcve.org
GlpiApplication · Glpi Project

CVE-2023-35940

HIGH · 7.5 CVSS v3.1 Published 2023-07-05
Fix available
A fix is available. Upgrade to 10.0.8 or later.
See remediation →
84/100
Remediation priority · High
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 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 file allows an unauthenticated user to be able to access dashboards 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 asset and IT management software versions 9.5.0 through 10.0.7 contain an incorrect access control check on a file that allows unauthenticated users to bypass authorization and access sensitive dashboard data. This is a broken access control/IDOR vulnerability enabling unauthorized information disclosure.

MitigationUpgrade GLPI to version 10.0.8 or later which contains the corrected rights validation. If immediate patching is not possible, restrict network access to the GLPI instance as a compensating control.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 (typically at /glpi/version.php) and read the $CFG_GLPI['version'] value, or check the footer of the GLPI web interface for the version number
    Affected if The version is 9.5.0 through 10.0.7 (inclusive)
  2. Verify GLPI is network-accessible
    Determine if the GLPI web interface is exposed to the internet or accessible from untrusted networks by reviewing firewall rules, reverse proxy configuration, or network ACLs
    Affected if GLPI is reachable from unauthenticated/untrusted network segments without proper access restrictions
  3. Identify the vulnerable endpoint
    Review web server access logs for unauthenticated requests to dashboard-related PHP files (such as front/dashboard.php, ajax/dashboard.php, or similar files in the /front/ or /ajax/ directories) that may expose sensitive data
    Affected if HTTP requests to dashboard-related endpoints succeed without requiring valid session authentication
  4. Check for unauthorized dashboard access
    Examine GLPI access logs for repeated unauthenticated GET requests to dashboard data endpoints, looking for successful 200 responses that indicate information disclosure
    Affected if HTTP status 200 responses are logged for dashboard data requests from unauthenticated IP addresses
  5. Review user session validation
    Inspect the PHP source code of the suspected vulnerable file to confirm that session validation or authorization checks are missing or improperly implemented before sensitive data is returned
    Affected if The code lacks proper session authentication checks (such as empty($_SESSION) or absent Session::checkRight() calls) before outputting dashboard data

If GLPI version is between 9.5.0 and 10.0.7 and the dashboard endpoints are accessible without authentication from your network, your environment is likely affected by this CVE.

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 corrected rights validation. If immediate patching is not possible, restrict network access to the GLPI instance as a compensating control.

Recommended fix High confidence

10.0.8

  1. Back up your GLPI database and files before upgrading
  2. Download GLPI version 10.0.8 from the official GLPI repository (github.com/glpi-project/glpi/releases)
  3. Extract the new version to your web server document root
  4. Copy the config directory from your existing installation to preserve your configuration
  5. Run the upgrade by accessing GLPI in a web browser and following the upgrade prompts, or use the command-line upgrade method
  6. Verify that the dashboard data is no longer accessible to unauthenticated users after the upgrade
Caveat Review GLPI 10.0.8 release notes for any breaking changes or required migration steps specific to your configuration

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

Fix this in Glpi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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