CVE-2020-5248 json
Public GLPIKEY can be used to decrypt any data in GLPI
published 2020-05-12 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-26461
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 74%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Exploit prediction
1.53% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- glpi-project glpi
Classification
- Weakness
-
- CWE-798 Use of Hard-coded Credentials
References
-
github.com
/glpi-project/glpi/commit/efd14468c92c4da43333aa9735e65fd20cbc7c6c
patch, third-party-advisory
-
github.com
/glpi-project/glpi/security/advisories/GHSA-j222-j9mf-h6j9
mitigation, third-party-advisory
Sources
- CVE List CVE-2020-5248
- NVD CVE-2020-5248
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.