Cross-Site Request Forgery (CSRF) in glpi-project/glpi


Reported on

Aug 5th 2021

✍️ Description

Attacker able to delete any document from Processing change with CSRF attack because there is any CSRF protection for related endpoint.

It does not matter at all that your application run in localhost or elsewhere, just it is enough to run on a browser and another low privilege user or attackers know the IP address or hostname of your application.

In CSRF attacks it is necessary that a user logged into your application just going to a malicious website and after that only with a redirection attacker can delete a Processing change document, this means only with visiting a site a Processing change document will be deleted.

🕵️‍♂️ Proof of Concept

1.fisrt user already should be logged in In Firefox or safari.

2.Open the PoC.html and click on submit button ( Also it can be auto-submit)

3.Here Processing change document with id 7 from change id equal to 1 will be deleted after clicking on submit button on PoC.html file.

// PoC.html

<script>history.pushState('', '', '/')</script>
<form action="">
<input type="hidden" name="delete&#95;document" value="" />
<input type="hidden" name="documents&#95;id" value="7" />
<input type="hidden" name="changes&#95;id" value="1" />
<input type="submit" value="Submit request" />

Also for real attacks the submit button can be auto-submit.

💥 Impact

This vulnerability is capable of delete any Processing change document.


set a token with a length bigger that 16 characters in every requests body then attacker never can guess the url. Also you cat turn Lax to Strict in cookies. 📍 Location index.php#L1

Am modified the report
3 years ago
3 years ago

Hey amammad, I've contacted the repo's maintainers for you.

We have contacted a member of the glpi-project/glpi team and are waiting to hear back 3 years ago
glpi-project/glpi maintainer
3 years ago


Hi amammad, I created a Github security advisory for your 4 CSRF reports.

glpi-project/glpi maintainer validated this vulnerability 3 years ago
am0o0 has been awarded the disclosure bounty
The fix bounty is now up for grabs
François Legastelois marked this as fixed in 9.5.6 with commit 93750e 2 years ago
François Legastelois has been awarded the fix bounty
to join this conversation