In reading and posting on this forum, I see a lot of code here that doesn't consider sql injection.
SQL injection is an attack where the attacker terminates or modifies an sql query with input data.
Here are some samples:
In Michael Howard's blog, he wrote up a very nice primer on this type of attack and why it's important to secure yourself against it.
Forget that this guy works for Microsoft, and this is a php forum, because all the same stuff applies to us.
I've wanted to write this up for just about every post I've seen here... There's a scary disregard for input filtering among most of these posts.
Some things he doesn't mention, which also help, is:
1. Limit the size of your parameters
If you are expecting no more than 10 characters, then substr($var, 0,10) the variable. The larger the string you allow, the more space an attacker has to work with malicious queries.
If you are expecting a 1 digit integer, then substr($var,0,1) and test it with is_int().
2. Use php's string handling functions
php has a ton of variable, sql filtering and format validation functions, use them 8) htmlentities() is very powerful for handling issues etc before handing the var off to the validation and filtering routines.
SQL injection is very serious and can lead to everything from stolen data, to defaced sites, to your site users getting infected with malware (by modifying links to point at counterfeit sites with malicious active x controls or 0day flash exploits). As a developer, it's your responsibility to filter your user input. You can filter it client side for user convenience, but it *absolutely* must be filtered at the posting processor (server side script) no matter what.