CVE-2025-53105
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 · uneditedGLPI, 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 10.0.0 to before 10.0.19, a connected user without administration rights can change the rules execution order. This issue has been patched 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 confidenceGLPI versions 10.0.0 through 10.0.18 contain a broken access control vulnerability where authenticated non-administrator users can modify the execution order of business rules. This allows privilege escalation by altering rule prioritization, potentially bypassing intended workflow controls.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify GLPI versionCheck the version number in the footer of any GLPI page, or look at the version file (glpi/inc/constant.php or version.php) in the installation directoryAffected if The version is 10.0.0 through 10.0.18 inclusive
-
Confirm business rules feature is activeNavigate to Administration > Business Rules (or Rules menu) in the GLPI web interface and verify the module is accessibleAffected if Business rules module is enabled and accessible in the UI
-
Identify authenticated user roleLog in as a non-administrator user account and check the user profile in Administration > Users > [user] > Profile tabAffected if The logged-in user has a profile WITHOUT Super-Admin or Administration rights
-
Test rule execution order modificationAs a non-admin user, attempt to access Business Rules > Rule Order or similar interface to reorder rules, and submit a changeAffected if Non-admin user can successfully access and modify the execution order of business rules
You are affected if running GLPI version 10.0.0-10.0.18 AND non-administrator users can access and modify business rule execution order, allowing potential privilege escalation through rule prioritization changes.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade GLPI to version 10.0.19 or later. Verify that non-admin users can no longer modify rule execution order after the patch.
GLPI 10.0.19
- Backup your GLPI database and files before upgrading
- Verify your current GLPI version is between 10.0.0 and 10.0.18
- Download GLPI version 10.0.19 from the official GitHub repository or your distribution method
- Follow the standard GLPI upgrade procedure: stop web server, replace files with new version, restart web server
- Run the migration script if prompted during first access after upgrade
- Log in and verify that non-admin users can no longer modify rule execution order in the administration interface
- Test that normal GLPI functionality remains intact
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53105 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-53105 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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