Learn Security

In a series of my findings in SeedDMS Software. A quick update, SeedDMS is a opensource software in which I have found Vulnerabilities like  RCE  and XSS . This article is focused on the XSS finding, I had found in the latest version of SeedDMS. Lets get into the Exploitation part to see how it can be reproduced. Login to the application and go to Groups Management in Admin tools. Now create a new group as hello<script>alert("group")</script> Now save it click on choose group to execute the JavaScript inserted above. P.S. I have already reported this to the vendor and they have patched it and issued an update for the same. https://sourceforge.net/p/seeddms/code/ci/master/tree/CHANGELOG

In a series of my findings in SeedDMS Software. A quick update, SeedDMS is a opensource software in which I have found Vulnerabilities like RCE and XSS . This article is focused on the XSS finding, I had found in the latest version of SeedDMS. Lets get into the Exploitation part to see how it can be reproduced. Login to the application and go to My account and edit user details. Change the name by adding <script>alert("name")</script> as shown in below image. Now browse to user management option in Admin-tools and click on choose user to execute the previously inserted javascript code. A key takeway from this finding is that while pentesting try injecting JS payloads very specific for example here I have used "name" rather than traditional "1" inside the alert box. Why? You might ask. Reason is simple you might not know when where sanitisation and validation is not in place, and your injected payload might get executed somewhe...

As of late, I have discovered a genuine vulnerability RCE (Remote Command Execution) in one of the open-source software to be specific “SeedDMS”. Through this vulnerability, an attacker can upload a backdoor/web shell and execute commands on the server.  Because of the security concerns and impediments, I wouldn't be uploading any snippets or screenshots here but would try to explain it as brief as could be expected under the circumstances.  How about we get into the Exploit part as follows: Sign in to the application and inside any folder upload a PHP web shell file (there is no restriction or validation on the uploaded file). Presently in URL, you can observe a document id corresponding to the file uploaded (This ID is actually the folder name, I will jump on to this towards the end of the blog as to how I learned about the same)  Now go to the following URL "example.com/data/1048576/DOCUMENT_ID/1.php"   That is it!!!... Right it might sound very st...