dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2025-27153

MEDIUM · 6.5 CVSS v3.1 Published 2025-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
Escalade GLPI plugin is a ticket escalation process helper for GLPI. Prior to version 2.9.11, there is an improper access control vulnerability. This can lead to data exposure and workflow disruptions. This issue has been patched in version 2.9.11.

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 · moderate confidence

The Escalade GLPI plugin before version 2.9.11 contains an improper access control vulnerability that allows unauthorized users to bypass intended permission boundaries, potentially exposing sensitive ticket escalation data and disrupting workflow processes.

MitigationUpgrade the Escalade GLPI plugin to version 2.9.11 or later to apply the access control fix. After patching, verify that role-based access controls for ticket escalation features function correctly.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate the Escalade plugin version in GLPI
    In the GLPI interface, navigate to Setup > Plugins, find the Escalade plugin in the list, and note the version number displayed. Alternatively, check the plugin's main PHP file header or version file in the plugins directory.
    Affected if The displayed version is lower than 2.9.11 (e.g., 2.9.10, 2.9.0, or any version before 2.9.11)
  2. Confirm the Escalade plugin is active
    In GLPI, go to Setup > Plugins and verify that the Escalade plugin shows as Active or Enabled, not just Installed.
    Affected if The plugin is installed AND active while the version is before 2.9.11
  3. Review escalation feature permissions in user profiles
    Navigate to Administration > Profiles in GLPI, select a profile, and inspect the permissions under the Escalade plugin section (or Tickets menu if the plugin integrates there). Check if escalation-related actions are assigned to standard user roles.
    Affected if Standard user profiles have access to escalation features that should be restricted to administrative or privileged roles
  4. Test for unauthorized escalation data access
    Log in as a non-privileged user (one without admin rights to the Escalade plugin), navigate to a ticket, and attempt to access escalation-related options, views, or data that should be restricted based on role definitions.
    Affected if A non-privileged user can view, modify, or trigger ticket escalations that they should not have permission to access
  5. Check audit logs for escalation actions by standard users
    In GLPI, access the activity log or audit logs (found under Administration > Logs or Setup > Logs) and search for escalation-related actions performed by users who should not have escalation permissions.
    Affected if Standard users are recorded performing escalation actions that should require elevated privileges

The environment is affected if the Escalade GLPI plugin version is below 2.9.11 AND the plugin is enabled, allowing unauthorized users to bypass access controls for escalation 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the Escalade GLPI plugin to version 2.9.11 or later to apply the access control fix. After patching, verify that role-based access controls for ticket escalation features function correctly.

Recommended fix Moderate confidence

2.9.11

  1. 1. Backup your current GLPI installation and database before making any changes.
  2. 2. Locate the Escalade plugin directory in your GLPI plugins folder (typically /glpi/plugins/ or /marketplace/).
  3. 3. Download Escalade plugin version 2.9.11 from the official GLPI plugin repository or GitHub.
  4. 4. Replace the existing Escalade plugin files with the new version 2.9.11.
  5. 5. Log into GLPI as an administrator.
  6. 6. Navigate to Setup > Plugins.
  7. 7. If the plugin is already installed, disable it first, then reinstall/upgrade to version 2.9.11.
  8. 8. Verify the plugin is running at version 2.9.11 in the plugins list.
Caveat Review plugin release notes for any breaking changes or configuration adjustments required after upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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