How severe is CVE-2020-5248?

CVE-2020-5248 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over local access with high attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2020-5248 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (70th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-5248?

CVE-2020-5248 affects Glpi-project Glpi. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2020-5248?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2020-5248 published?

CVE-2020-5248 was published on 2020-05-12 and last updated on 2026-06-17.

CVE-2020-5248

CVE-2020-5248 is a high-severity vulnerability in Glpi-project Glpi with a CVSS 3.x base score of 7.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-798.

Key facts

Severity: High (CVSS 3.x base score 7.2)
CVSS v2: 5.0
EPSS exploit prediction: 1% (70th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-798
Affected product: Glpi-project Glpi
Published: 2020-05-12
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is 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.
How severe is CVE-2020-5248?: CVE-2020-5248 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over local access with high attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2020-5248 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (70th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-5248?: CVE-2020-5248 affects Glpi-project Glpi. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-5248?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2020-5248 published?: CVE-2020-5248 was published on 2020-05-12 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:glpi-project:glpi:*:*:*:*:*:*:*:*

More vulnerabilities in Glpi-project Glpi

CVE-2023-42802 — Critical (CVSS 10.0): GLPI is a free asset and IT management software package. Starting in version 10.0.7 and prior to version 10.0.10, an…
CVE-2023-28849 — Critical (CVSS 10.0): GLPI is a free asset and IT management software package. Starting in version 10.0.0 and prior to version 10.0.7, GLPI…
CVE-2022-35947 — Critical (CVSS 10.0): GLPI stands for Gestionnaire Libre de Parc Informatique and is a Free Asset and IT Management Software package, that…
CVE-2025-21619 — Critical (CVSS 9.8): GLPI is a free asset and IT management software package. An administrator user can perfom a SQL injection through the…
CVE-2022-35914 — Critical (CVSS 9.8): /vendor/htmlawed/htmlawed/htmLawedTest.php in the htmlawed module for GLPI through 10.0.2 allows PHP code injection.
CVE-2022-31061 — Critical (CVSS 9.8): GLPI is a Free Asset and IT Management Software package, Data center management, ITIL Service Desk, licenses tracking…

All CVEs affecting Glpi-project Glpi →

Other CWE-798 (Use of Hard-coded Credentials) vulnerabilities

CVE-2026-13768 — Critical (CVSS 10.0): Gardyn devices expose a privileged iothubowner key. Access to this key will allow a malicious user to invoke an IoTHub…
CVE-2026-45631 — Critical (CVSS 10.0): Dokploy is a free, self-hostable Platform as a Service (PaaS). From 0.27.0 to before 0.29.3, a hardcoded…
CVE-2026-22769 — Critical (CVSS 10.0): Dell RecoverPoint for Virtual Machines, versions prior to 6.0.3.1 HF1, contain a hardcoded credential vulnerability.…
CVE-2025-42890 — Critical (CVSS 10.0): SQL Anywhere Monitor (Non-GUI) baked credentials into the code,exposing the resources or functionality to unintended…
CVE-2025-7503 — Critical (CVSS 10.0): An OEM IP camera manufactured by Shenzhen Liandian Communication Technology LTD exposes a Telnet service (port 23) with…
CVE-2025-20309 — Critical (CVSS 10.0): A vulnerability in Cisco Unified Communications Manager (Unified CM) and Cisco Unified Communications Manager Session…

Browse all CWE-798 (Use of Hard-coded Credentials) vulnerabilities →