#VU30290 Use of hard-coded credentials in GLPI - CVE-2020-5248
Published: May 12, 2020 / Updated: November 14, 2025
Vulnerability identifier: #VU30290
Vulnerability risk: Medium
CVSSv4.0: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/U:Green
CVE-ID: CVE-2020-5248
CWE-ID: CWE-798
Exploitation vector: Remote access
Exploit availability:
Public exploit is available
Vulnerable software:
GLPI
GLPI
Software vendor:
glpi-project
glpi-project
Description
The vulnerability allows a remote non-authenticated attacker to gain access to sensitive information.
GLPI before before version 9.4.6 has a vulnerability involving a default encryption key. GLPIKEY is public and is used on every instance. This means anyone can decrypt sensitive data stored using this key. It is possible to change the key before installing GLPI. But on existing instances, data must be reencrypted with the new key. Problem is we can not know which columns or rows in the database are using that; espcially from plugins. Changing the key without updating data would lend in bad password sent from glpi; but storing them again from the UI will work.
Remediation
Install update from vendor's website.