CVE-2020-15176

SQL injection in GLPI

Description

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

Category

8.7
CVSS
Severity: High
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.28%
Third-Party Advisory github.com Third-Party Advisory github.com
Affected: glpi-project glpi
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2020-15176?
CVE-2020-15176 has been scored as a high severity vulnerability.
How to fix CVE-2020-15176?
To fix CVE-2020-15176, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2020-15176 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2020-15176 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2020-15176?
CVE-2020-15176 affects glpi-project glpi.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.