<?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>Mon, 06 Oct 2008 18:32:34 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Zend Developer Zone: Avoiding XSS security attacks to sites that use HTML editors]]></title>
      <guid>http://www.phpdeveloper.org/news/7512</guid>
      <link>http://www.phpdeveloper.org/news/7512</link>
      <description><![CDATA[<p>
In <a href="http://devzone.zend.com/node/view/id/1752">an article</a> from the Zend Developer Zone by <i>Manuel Lemos</i>, there's a look at how to avoid cross-site scripting security attacks on a site that allows users to input information via a HTML editor.
</p>
<blockquote>
<p>
HTML editors are great. However, care must be taken to avoid security abuses. An application that uses HTML editors, expects that the submitted HTML content comes correctly formatted and well-formed. That happens when real users use real browsers to edit the content.
</p>
<p>
However, an attacker may create a program that pretends to be a real browser and submit specially crafted HTML with Javascript that may open security holes.
</p>
</blockquote>
<p>
<i>Manuel</i> talks a bit about what cross-site scripting means in this context and a simple (Javascript) example of how a user could abuse it. His solution? Parse the incoming data (filter it!) and look for potentially harmful tag types. To do this, he recommends the <a href="http://www.phpclasses.org/inputfilter">PHP Input Filter</a> class. There's even a simple example of how to use it included in the post.
</p>]]></description>
      <pubDate>Tue, 27 Mar 2007 10:03:00 -0500</pubDate>
    </item>
  </channel>
</rss>
