query: Not sanitizing purposely for SQL Injection
positive_passages.docid: 38732
positive_passages.text: How does the SQL injection from the "Bobby Tables" XKCD comic work?
negative_passages.docid: 156732
negative_passages.text: Using wildcards in prepared statement - MySQLi
negative_passages.docid: 101638
negative_passages.text: How do I make sure that values from MySQL keep their type in PHP?
negative_passages.docid: 74406
negative_passages.text: SQL injection that gets around mysql_real_escape_string()
negative_passages.docid: 8240
negative_passages.text: How to secure database passwords in PHP?
negative_passages.docid: 60773
negative_passages.text: Can I parameterize the table name in a prepared statement?
negative_passages.docid: 74188
negative_passages.text: How can I avoid SQL injection attacks in my ASP.NET application?
negative_passages.docid: 20926
negative_passages.text: PHP protection of GET parameters
negative_passages.docid: 107222
negative_passages.text: Exploitable PHP functions
negative_passages.docid: 26044
negative_passages.text: Obfuscate PHP code
negative_passages.docid: 122816
negative_passages.text: SQL injection with php filtering
negative_passages.docid: 139754
negative_passages.text: How do I escape a single quote in SQL Server?
negative_passages.docid: 158241
negative_passages.text: Will using LINQ to SQL help prevent SQL injection
negative_passages.docid: 132935
negative_passages.text: Does LINQ's ExecuteCommand provide protection from SQL injection attacks?
negative_passages.docid: 98052
negative_passages.text: PHP Markdown XSS Sanitizer
negative_passages.docid: 89756
negative_passages.text: Using a variable instead of a parameter index with a JDBC prepared statement
negative_passages.docid: 90507
negative_passages.text: Parameter Sniffing (or Spoofing) in SQL Server