CVE-2026-57150 in GLPIinfo

Summary

by MITRE • 11/16/2026

GLPI is a free asset and IT management software package. Prior to 10.0.28, 11.0.10, and 12.0.1, authenticated users can craft a URL that invokes massive actions without all required object- and action-specific authorization checks. The bypass permits operations outside the user's granted rights, including unauthorized plugin activation, deactivation, and uninstallation for plugins already present on the filesystem and other state-changing maintenance actions. This issue is fixed in versions 10.0.28, 11.0.10, and 12.0.1.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 11/16/2026

GLPI serves as a comprehensive open-source asset and IT management software package widely deployed for tracking hardware, software, and network infrastructure within enterprise environments. The vulnerability identified in versions prior to GLPI 10.0.28, 11.0.10, and 12.0.1 represents a critical failure in access control mechanisms specifically affecting authenticated users. While the system correctly enforces permissions for individual object-level operations, it fails to implement adequate authorization checks when processing bulk or massive actions through crafted URLs. This architectural flaw allows an attacker who has valid credentials but limited privileges to bypass security controls by manipulating request parameters associated with mass action handlers.

The core technical flaw lies in the server-side validation logic that processes batched requests. When a user initiates a massive action, such as modifying multiple items simultaneously or executing administrative tasks on behalf of several objects, the application does not sufficiently verify whether the initiating user possesses the specific rights required for each individual object and action type involved in the request. Consequently, an authenticated low-privilege user can construct malicious URLs that invoke these mass actions without triggering the necessary authorization checks. This bypass effectively neutralizes the principle of least privilege by allowing operations that should be restricted to administrators or users with elevated roles.

The operational impact of this vulnerability is significant due to the nature of GLPI as a central management platform for IT infrastructure. An attacker exploiting this flaw can perform unauthorized plugin activation, deactivation, and uninstallation for plugins already present on the filesystem. Since plugins often extend core functionality and may introduce additional attack surfaces or administrative capabilities, their manipulation can lead to further compromise. Furthermore, the ability to execute other state-changing maintenance actions outside of granted rights enables an attacker to disrupt service availability, alter configuration states, or potentially escalate privileges by enabling malicious extensions that could facilitate remote code execution or data exfiltration in subsequent stages of an attack chain.

This vulnerability aligns with CWE-269, which describes Improper Privilege Management, as the system fails to enforce appropriate access control levels for specific actions based on user roles. Additionally, it relates to ATT&CK technique T1078, Valid Accounts, because exploitation requires initial authentication but leverages flawed logic to exceed those account's permissions. The lack of granular authorization checks during bulk operations highlights a common oversight in web application development where individual item validation is prioritized over aggregate request integrity verification.

To mitigate this risk, organizations must immediately upgrade GLPI to version 10.0.28, 11.0.10, or 12.0.1 and later, as these releases contain the necessary patches for authorization checks in mass action handlers. Until an upgrade is feasible, administrators should restrict access to GLPI instances using network-level controls such as firewalls or reverse proxies that limit exposure to trusted IP addresses only. Implementing strict role-based access control policies and regularly auditing user permissions can also help minimize the potential impact if exploitation occurs. Continuous monitoring of system logs for unusual mass action requests from low-privilege accounts is recommended to detect potential attempts at exploiting this vulnerability before significant damage is incurred.

Responsible

GitHub M

Reservation

06/24/2026

Disclosure

11/16/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Want to stay up to date on a daily basis?

Enable the mail alert feature now!