CVSS 3.1
5.3 mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NCVE-2020-5248
Medium (5.3) in glpi-project glpi. EPSS 1.5% chance of exploitation in the next 30 days.
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.
Severity
- EPSS
- 1.5% chance of exploitation in the next 30 days; higher than 74% of CVEs (scores of 2026-10-31)
- CWE
- CWE-798
- Published
- Modified
- Record from
- the NVD, synced
Affected
- glpi-project:glpi
References
- https://github.com/glpi-project/glpi/commit/efd14468c92c4da43333aa9735e65fd20cbc7c6c
- https://github.com/glpi-project/glpi/security/advisories/GHSA-j222-j9mf-h6j9
- https://github.com/glpi-project/glpi/commit/efd14468c92c4da43333aa9735e65fd20cbc7c6c
- https://github.com/glpi-project/glpi/security/advisories/GHSA-j222-j9mf-h6j9