Back to Database
Status published
High
CVE-2020-11031
Insecure encryption algorithm in GLPI
Vulnerability Description
In GLPI before version 9.5.0, the encryption algorithm used is insecure. The security of the data encrypted relies on the password used, if a user sets a weak/predictable password, an attacker could decrypt data. This is fixed in version 9.5.0 by using a more secure encryption library. The library chosen is sodium.
Impact Analysis
Refer to official advisory for detailed impact metrics.
Remediation
Ensure systems are updated to the latest vendor-supplied patch levels.
THREAT MONITOR
Am I Vulnerable?
Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2020-11031
Credits & Attribution
No credits recorded in the NVD database.
References
More from glpi-project
View All →CVE-2025-66417
GLPI has an unauthenticated SQL injection through the inventory endpoint
High
7.5
CVE-2025-64520
GLPI vulnerable to unauthorized access to restricted Knowledge Base items through the API
Medium
6.5
CVE-2025-64516
GLPI incorrectly authorizes access to documents
High
7.5
CVE-2025-59935
GLPI Vulnerable to Unauthenticated Stored XSS on the Inventory page
Medium
6.5
CVE-2025-53357
GLPI permits reservation modification by unauthorized users
Medium
5.4
Affected Vendor
glpi-project
View all reports →Affected Software
GLPI
Vulnerable Versions:
< 9.5.0
Timeline
Official Publish:
September 23rd, 2020
Last Modified:
August 4th, 2024
Added to House:
July 21st, 2026
CVSS Vectors
V3:
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N