disease @disease

warning!

From the tests i have done, there are many vulnerabilities on this website, there are also a lot of bugs. Example: when posting something, if you spam click `post` it will create a post for every time you click the button, there should be an implementation to limit the time between posts and to make the button a one time click. (THIS BUG MAKES THE SITE LAG!). its also a pain to delete all of the posts if you accidentally do so as the site refreshes but will still lag and there is a small chance that the post will not be deleted. There is also a password vulnerability… maybe don’t have the user’s passwords get stored as a plain document.

THERE ARE VULNERABILITIES IN THE REPO!; Yes, even tho the repo is the legacy site and isn’t used anymore it is still good to state the vulnerabilities on the repo as people might use the template to make their own site like this and wont know of the vulnerabilities in the code:

List of the vulnerabilities on the repo: SQL Injection, Cross-Site Scripting (XSS), Insecure Direct Object Reference (IDOR), Lack of Input Validation, Insecure, Outdated Dependencies, Lack of Error Handling, Insecure Session Managemen, Storage of Sensitive Data(user and password information: Insecure Password Storage, Weak Password Hashing, Lack of Password Salting, Insecure Password Verification, Missing Password Complexity Requirements, insecure Password Reset Token Generation, insecure Password Storage in Sessions), Lack of Secure Communication… sry <3

Aug 16, 2024, 2:18 PM
25
View all Parent

comments

Highlighted comment

well, you can do a "NoSQL injection" or a "MongoDB injection." which are practically the same thing as a “SQL injection“… also, that list is for the vulnerabilities in the repo <3

It’s much trickier to pull off, the web application would have to accept a JSON object in a place where other MongoDB operators can be used to find/update other documents you don’t have access to. As a cyber-security expert as you claim to be, maybe you should responsibly disclose vulnerabilities before making them public? Anyway, if you find any, please reach out using one of the methods on https://wasteof.money/security.txt