Vulnerability in Glpi-Project Glpi
CVE-2020-5248
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.2 (High). Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N.
EPSS exploit prediction
EPSS 0.015, 75.1th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Glpi-Project Glpi — versions < 9.4.6
Weakness classification (CWE)
Public exploits and proof-of-concept code
3 public repositories with exploit or proof-of-concept code for this CVE:
- venomnis/CVE-2020-5248 (6 stars, last pushed 2025-09-25): Proof of Concept (PoC) for CVE-2020-5248.
- Mkway/CVE-2020-5248 (last pushed 2021-07-29): CVE-2020-5248
- indevi0us/CVE-2020-5248
Also mentioned in 8 other repositories (ARPSyndicate/cvemon, ARPSyndicate/cve-scores, developer3000S/PoC-in-GitHub, …). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- github.com/glpi-project/glpi/security/advisories/GHSA-j222-j9mf-h6j9 (Third Party Advisory, Mitigation)
- github.com/glpi-project/glpi/commit/efd14468c92c4da43333aa9735e65fd20cbc7c6c (Patch, Third Party Advisory)
This CVE has public exploit evidence. See the latest CVEs with public exploits.