Filtered by vendor Glpi-project
Subscriptions
Filtered by product Glpi
Subscriptions
Total
129 CVE
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2020-15108 | 1 Glpi-project | 1 Glpi | 2020-07-22 | 7.1 High |
| In glpi before 9.5.1, there is a SQL injection for all usages of "Clone" feature. This has been fixed in 9.5.1. | ||||
| CVE-2020-5248 | 1 Glpi-project | 1 Glpi | 2020-05-14 | 5.3 Medium |
| 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. | ||||
| CVE-2020-11062 | 1 Glpi-project | 1 Glpi | 2020-05-14 | 5.4 Medium |
| In GLPI after 0.68.1 and before 9.4.6, multiple reflexive XSS occur in Dropdown endpoints due to an invalid Content-Type. This has been fixed in version 9.4.6. | ||||
| CVE-2020-11032 | 1 Glpi-project | 1 Glpi | 2020-05-07 | 7.2 High |
| In GLPI before version 9.4.6, there is a SQL injection vulnerability for all helpdesk instances. Exploiting this vulnerability requires a technician account. This is fixed in version 9.4.6. | ||||
| CVE-2013-2227 | 2 Debian, Glpi-project | 2 Debian Linux, Glpi | 2019-11-04 | 7.5 High |
| GLPI 0.83.7 has Local File Inclusion in common.tabs.php. | ||||
| CVE-2019-1010307 | 1 Glpi-project | 1 Glpi | 2019-07-18 | N/A |
| GLPI GLPI Product 9.3.1 is affected by: Cross Site Scripting (XSS). The impact is: All dropdown values are vulnerable to XSS leading to privilege escalation and executing js on admin. The component is: /glpi/ajax/getDropDownValue.php. The attack vector is: 1- User Create a ticket , 2- Admin opens another ticket and click on the "Link Tickets" feature, 3- a request to the endpoint fetches js and executes it. | ||||
| CVE-2019-13240 | 1 Glpi-project | 1 Glpi | 2019-07-17 | N/A |
| An issue was discovered in GLPI before 9.4.1. After a successful password reset by a user, it is possible to change that user's password again during the next 24 hours without any information except the associated email address. | ||||
| CVE-2019-13239 | 1 Glpi-project | 1 Glpi | 2019-07-08 | N/A |
| inc/user.class.php in GLPI before 9.4.3 allows XSS via a user picture. | ||||
| CVE-2019-10477 | 2 Fusioninventory, Glpi-project | 2 Fusioninventory, Glpi | 2019-04-01 | N/A |
| The FusionInventory plugin before 1.4 for GLPI 9.3.x and before 1.1 for GLPI 9.4.x mishandles sendXML actions. | ||||
| CVE-2018-13049 | 1 Glpi-project | 1 Glpi | 2018-08-30 | N/A |
| The constructSQL function in inc/search.class.php in GLPI 9.2.x through 9.3.0 allows SQL Injection, as demonstrated by triggering a crafted LIMIT clause to front/computer.php. | ||||
| CVE-2018-7562 | 1 Glpi-project | 1 Glpi | 2018-04-11 | N/A |
| A remote code execution issue was discovered in GLPI through 9.2.1. There is a race condition that allows temporary access to an uploaded executable file that will be disallowed. The application allows an authenticated user to upload a file when he/she creates a new ticket via front/fileupload.php. This feature is protected using different types of security features like the check on the file's extension. However, the application uploads and creates a file, though this file is not allowed, and then deletes the file in the uploadFiles method in inc/glpiuploaderhandler.class.php. | ||||
| CVE-2018-7563 | 1 Glpi-project | 1 Glpi | 2018-04-11 | N/A |
| An issue was discovered in GLPI through 9.2.1. The application is affected by XSS in the query string to front/preference.php. An attacker is able to create a malicious URL that, if opened by an authenticated user with debug privilege, will execute JavaScript code supplied by the attacker. The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes. | ||||
| CVE-2017-11475 | 1 Glpi-project | 1 Glpi | 2017-08-29 | N/A |
| GLPI before 9.1.5.1 has SQL Injection in the condition rule field, exploitable via front/rulesengine.test.php. | ||||
| CVE-2016-7508 | 1 Glpi-project | 1 Glpi | 2017-08-12 | N/A |
| Multiple SQL injection vulnerabilities in GLPI 0.90.4 allow an authenticated remote attacker to execute arbitrary SQL commands by using a certain character when the database is configured to use Big5 Asian encoding. | ||||
| CVE-2017-11183 | 1 Glpi-project | 1 Glpi | 2017-08-07 | N/A |
| front/backup.php in GLPI before 9.1.5 allows remote authenticated administrators to delete arbitrary files via a crafted file parameter. | ||||
| CVE-2017-11184 | 1 Glpi-project | 1 Glpi | 2017-08-04 | N/A |
| SQL injection exists in front/devicesoundcard.php in GLPI before 9.1.5 via the start parameter. | ||||
| CVE-2016-7509 | 1 Glpi-project | 1 Glpi | 2017-07-25 | N/A |
| Cross-site scripting (XSS) vulnerability in GLPI 0.90.4 allows remote authenticated attackers to inject arbitrary web script or HTML by attaching a crafted HTML file to a ticket. | ||||
| CVE-2016-7507 | 1 Glpi-project | 1 Glpi | 2017-07-25 | N/A |
| Cross-Site Request Forgery (CSRF) vulnerability in GLPI 0.90.4 allows remote authenticated attackers to submit a request that could lead to the creation of an admin account in the application. | ||||
| CVE-2017-11474 | 1 Glpi-project | 1 Glpi | 2017-07-21 | N/A |
| GLPI before 9.1.5.1 has SQL Injection in the $crit variable in inc/computer_softwareversion.class.php, exploitable via ajax/common.tabs.php. | ||||
| CVE-2015-7684 | 1 Glpi-project | 1 Glpi | 2015-10-06 | N/A |
| Unrestricted file upload in GLPI before 0.85.3 allows remote authenticated users to execute arbitrary code by adding a file with an executable extension as an attachment to a new ticket, then accessing it via a direct request to the file in files/_tmp/. | ||||