SQL Injection in Glpi-Project Glpi
CVE-2020-15176
In GLPI before version 9.5.2, when supplying a back tick in input that gets put into a SQL query,the application does not escape or sanitize allowing for SQL Injection to occur. Leveraging this vulnerability an attacker is able to exfiltrate sensitive information like passwords, reset tokens, personal details, and more. The issue is patched in version 9.5.2
Vulnerability class: SQL Injection
Published · last modified .
CVSS v3 metric
CVSS v3 base score 8.7 (High). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N.
EPSS exploit prediction
EPSS: 0.011 (65.6th percentile), scored .
Low probability of exploitation in the next 30 days, but still tracked. 66th percentile — 65.6% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.011 · newest: 0.011 · change: 0.000
Affected products
- Glpi-Project Glpi — versions >= 0.6.8, < 9.5.2
Weakness classification (CWE)
Public proof-of-concept exploits
References
- github.com/glpi-project/glpi/security/advisories/GHSA-x93w-64x9-58qw (Third Party Advisory)
- github.com/glpi-project/glpi/commit/f021f1f365b4acea5066d3e57c6d22658cf32575 (Patch, Third Party Advisory)
Frequently asked questions
- What is CVE-2020-15176?
- CVE-2020-15176 is a high-severity vulnerability in Glpi-Project Glpi, classified under SQL Injection. CVSS score: 8.7/10. Published 2020-10-07.
- How severe is CVE-2020-15176?
- High severity. CVSS v3 base score is 8.7 out of 10.
- Is CVE-2020-15176 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.