-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PHP Backend Input Sanitizing #9
Comments
I wanted to put this in with #7, You may have to educate me on how to do that lol. |
You only need to make one issue which covers the whole problem which you already did but it's not a problem. Rather than having millions of issues with the same thing just make one and use it. We'll use this one for now. Don't worry about assigning people either. Usually us dev's do that 😉 |
If you find any more examples where sanitizing needs to be done, put them in here please |
sure, how do I do that? I tried to add this to the previous one. You can tell im getting into it now, assigning people and adding labels, Whooo. 😆 🤦♂ I wont do this every day 😆 I'll do a few and come back a few days later. I don't wona be that annoying, only a little bit annoying 😄 |
Good on you! Haha Do the selecting an area of code like normal, but instead of clicking "Reference in New Issue" click the "Copy Permalink" one. Then go to comment like normal and paste the link |
asset-tracker-web/api/assets/deallocate/index.php Lines 27 to 31 in c31e5f8
This input $id will need filtering and the query will need putting in a prepared statement. |
asset-tracker-web/api/user/add/index.php
Lines 11 to 17 in 53b5078
Believe 'BuidQuery' function will need prepared statements and filtering/sanitizing. @matthewward00 #7
The text was updated successfully, but these errors were encountered: