We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Please use placeholders when doing SQL queries. For example:
$data = $DB->execute("UPDATE {auth_otp_linked_login} SETconfirmtoken= null,otpcreated= null wherephone = '" . $phone . "'"); $sql = 'select * from {auth_otp_linked_login} wherephone= ' . $username . ' ANDconfirmtoken= ' . $password; Instead of the second query, you can use $DB->get_records(). See https://docs.moodle.org/dev/Security:SQL_injection
$data = $DB->execute("UPDATE {auth_otp_linked_login} SET
= null,
= null where
= '" . $phone . "'");
$sql = 'select * from {auth_otp_linked_login} where
= ' . $username . ' AND
= ' . $password;
The text was updated successfully, but these errors were encountered:
this isn't fixed either... and it's a definite blocker.
Sorry, something went wrong.
Merge pull request #7 from sinthy08/bug_fix
02628ff
Fixed issues #2, #3, #5
nawazsharif
No branches or pull requests
Please use placeholders when doing SQL queries. For example:
$data = $DB->execute("UPDATE {auth_otp_linked_login} SET
confirmtoken= null,
otpcreated= null where
phone= '" . $phone . "'");
$sql = 'select * from {auth_otp_linked_login} where
phone= ' . $username . ' AND
confirmtoken= ' . $password;
Instead of the second query, you can use $DB->get_records(). See https://docs.moodle.org/dev/Security:SQL_injection
The text was updated successfully, but these errors were encountered: