dbcve.org
GlpiApplication · Glpi Project

CVE-2025-25192

MEDIUM · 6.5 CVSS v3.1 Published 2025-02-25
Fix available
A fix is available. Upgrade to 10.0.18 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. Prior to version 10.0.18, a low privileged user can enable debug mode and access sensitive information. Version 10.0.18 contains a patch. As a workaround, one may delete the `install/update.php` file.

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

In GLPI versions prior to 10.0.18, a low-privileged user can enable debug mode which exposes sensitive information including potentially configuration details, session data, or internal system paths. The debug functionality should be restricted to administrator-level accounts but was accessible to any authenticated user.

MitigationUpgrade to GLPI version 10.0.18 or later to receive the patch. Alternatively, delete the `install/update.php` file as a workaround, though upgrading is the recommended solution.

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.18

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 installed GLPI version
    Locate the GLPI version file or admin panel version display. Common locations include the footer of the GLPI interface, a version.php file in the inc/ directory, or the config table in the database.
    Affected if The installed version is any release prior to 10.0.18 (e.g., 10.0.17, 10.0.16, 10.0.10, 9.x, etc.)
  2. Verify debug mode accessibility for non-admin users
    Create or use a test account with low-privileged rights (e.g., a standard user or technician role without admin privileges). Attempt to access debug mode settings or enable debug mode through the user interface, profile settings, or by modifying user preferences.
    Affected if A user with non-administrator rights can successfully enable or access debug mode functionality
  3. Inspect debug mode configuration
    Check the GLPI configuration database or config files for debug mode settings. Look for debug_enabled, debug mode flags, or similar configuration entries that control whether debug is active.
    Affected if Debug mode configuration exists and can be modified by users without administrator-level privileges

Your environment is affected if the installed GLPI version is below 10.0.18 AND low-privileged authenticated users can access or enable debug mode features.

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.18 or later
Fixed in 10.0.18
Interim mitigation

Upgrade to GLPI version 10.0.18 or later to receive the patch. Alternatively, delete the `install/update.php` file as a workaround, though upgrading is the recommended solution.

Recommended fix High confidence

GLPI 10.0.18

  1. 1. Backup your GLPI database and files before upgrading.
  2. 2. Download GLPI version 10.0.18 from the official GitHub repository or glpi-project.org.
  3. 3. Extract the new version files to your web server document root.
  4. 4. Run the upgrade process by accessing GLPI in your browser and following the upgrade wizard.
  5. 5. Alternatively, if immediate upgrade is not possible, delete the `install/update.php` file as a workaround: locate the file in your GLPI installation directory and remove it.
Caveat Review the official GLPI 10.0.18 release notes for any breaking changes before upgrading, especially if upgrading across multiple minor versions.

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

Fix this in Glpi Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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