-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
SQLi Injection #47
Comments
Personally I think that using escape_string() is easier :) |
Easy but not as effective and if its not as effective that defeats the purpose. |
But at least it covers the vulnerability :) |
No it would not be sufficient for a web application it at this level. You need to use prepared statements. |
why? |
Fixed in v2.12 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please take a look at using Prepared Statements the ServerAuthWebAPI.php is just waiting to be exploited. Way too many SQL Injections exist.
For example:
Where $player = "1' or '1' = '1";
to demonstrate this issue. The result would be true.
The text was updated successfully, but these errors were encountered: