dbcve.org
GlpiApplication · Glpi Project

CVE-2025-53357

MEDIUM · 5.4 CVSS v3.1 Published 2025-07-30
Fix available
A fix is available. Upgrade to 10.0.19 or later.
See remediation →
60/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, which stands for Gestionnaire Libre de Parc Informatique, is a Free Asset and IT Management Software package, that provides ITIL Service Desk features, licenses tracking and software auditing. In versions 0.78 through 10.0.18, a connected user can alter the reservations of another user. This is fixed in version 10.0.19.

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

This is a broken access control (likely IDOR) vulnerability in GLPI's reservation management system. An authenticated user can modify reservations belonging to other users due to insufficient authorization checks on reservation modification endpoints.

MitigationUpgrade GLPI to version 10.0.19 or later to obtain the vendor patch. Verify that reservation authorization controls function correctly after upgrade.

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.78, < 10.0.19

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 your GLPI version
    Locate the GLPI version number in the application (typically found in the footer of the web interface, in a version.php file, or in the database configuration table)
    Affected if The installed version is 0.78 or higher but lower than 10.0.19
  2. Confirm the reservation module is active
    Verify that the Reservations feature is enabled in your GLPI instance - check the GLPI configuration or plugin status to confirm the reservation management system is installed and active
    Affected if The reservation management module is enabled and the version check shows a vulnerable version
  3. Identify reservation modification endpoints
    Examine the web application routes or URL patterns used for reservation modification actions (typically URLs containing 'reservation' and action parameters like 'update' or 'modify')
    Affected if Reservation modification endpoints exist and the version is vulnerable
  4. Test for unauthorized reservation modification
    As an authenticated user with standard privileges, attempt to modify a reservation known to belong to a different user by manipulating the reservation ID parameter in modification requests
    Affected if You can successfully modify another user's reservation without proper authorization errors
  5. Review reservation access control logs
    Check GLPI application logs or audit trails for reservation modification events to identify any unauthorized cross-user reservation changes
    Affected if Logs show modification of reservations by users who do not own those reservations

Your environment is affected if GLPI version is 0.78 or higher but below 10.0.19 and the reservation management module is enabled, allowing authenticated users to modify reservations they do not own.

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.19 or later
Fixed in 10.0.19
Interim mitigation

Upgrade GLPI to version 10.0.19 or later to obtain the vendor patch. Verify that reservation authorization controls function correctly after upgrade.

Recommended fix High confidence

10.0.19

  1. Create a complete backup of your GLPI database and files before proceeding
  2. Download GLPI version 10.0.19 from the official GLPI website or GitHub repository
  3. Extract the new version files to replace your current installation
  4. Run the GLPI migration script/updater by accessing the glpi/install/ directory via web browser
  5. Follow the on-screen prompts to complete the database migration to version 10.0.19
  6. Verify that the upgrade completed successfully by logging into GLPI
  7. Test that users can no longer modify other users' reservations (IDOR vulnerability is fixed)
Caveat Minor version upgrades within 10.x typically have minimal breaking changes; always test in staging first

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

Fix this in Glpi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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