CVE-2025-66417
BaseFortify
Publication date: 2026-01-15
Last updated on: 2026-01-15
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| glpi_project | glpi | From 11.0.0 (inc) to 11.0.2 (inc) |
| glpi_project | glpi | 11.0.3 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-66417 is a high-severity SQL injection vulnerability in the GLPI software versions 11.0.0 through 11.0.2. It allows an unauthenticated attacker to perform SQL injection attacks remotely without any privileges or user interaction. The vulnerability occurs because the software improperly constructs SQL commands using user-supplied input without properly escaping special SQL characters, leading to improper handling of inputs and enabling unauthorized database queries. [1]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing an attacker to access confidential data stored in the GLPI database without authorization. Although it does not affect data integrity or availability, the unauthorized data disclosure can lead to sensitive information exposure. Since the attack requires no privileges or user interaction and can be performed remotely, it poses a significant security risk. [1]
What immediate steps should I take to mitigate this vulnerability?
Upgrade GLPI to version 11.0.3 or later, as this version contains the fix for the SQL injection vulnerability. This is the recommended and effective mitigation step. [1]