<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Wed, 19 Jun 2013 19:10:48 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Chris Shiflett's Blog: The Unexpected SQL Injection]]></title>
      <guid>http://www.phpdeveloper.org/news/8753</guid>
      <link>http://www.phpdeveloper.org/news/8753</link>
      <description><![CDATA[<p>
<i>Chris Shiflett</i> <a href="http://shiflett.org/blog/2007/sep/the-unexpected-sql-injection">points out</a> an unexpected SQL injection possibility as presented by <a href="http://mordred.niama.net/blog/">Alexander Andonov</a> for PHP (involving mysql_real_escape_string).
</p>
<blockquote>
The focus of the article is stressing the importance of filtering input and escaping output, as neither is a substitute for the other, but he does so very clearly with specific examples [...] A number of example exploits are supplied for each case, and he discusses which ones work, which ones don't, and why.
</blockquote>
<p>
<i>Chris</i> also uses the post to link to <a href="http://preinheimer.com/">Paul Reinheimer</a>'s post about <a href="http://blog.preinheimer.com/index.php?/archives/247-addslashes-vs-mysql_escape_string.html">add_slashes versus mysql_escape_string</a> and his <a href="http://shiflett.org/blog/2006/jan/addslashes-versus-mysql-real-escape-string">own post</a> on the same topic.
</p>]]></description>
      <pubDate>Mon, 01 Oct 2007 08:47:00 -0500</pubDate>
    </item>
  </channel>
</rss>
