<?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>Fri, 24 May 2013 22:08:04 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Gareth Heyes' Blog: PHP self return of the slash]]></title>
      <guid>http://www.phpdeveloper.org/news/13286</guid>
      <link>http://www.phpdeveloper.org/news/13286</link>
      <description><![CDATA[<p>
In <a href="http://www.thespanner.co.uk/2009/09/25/php-self-return-of-the-slash/">this new post</a> to his blog <i>Gareth Heyes</i> points out a legacy issue that those running older PHP4-based code might want to look into:
</p>
<blockquote>
I thought about something I found ages ago in PHP4 and it's been long enough now. This is also quite funny because my server is vulnerable to this. So what happens if you escape PHP_SELF with htmlentities($_SERVER['PHP_SELF'], ENT_QUOTES)? Safe from XSS? I hope so. Safe from everything? Well not really or at least it didn't used to be.
</blockquote>
<p>
He gives a <a href="http://www.businessinfo.co.uk/labs/php_self/login.php">simple example</a> of how the PHP_SELF issue can be used to change the form's target just by using a few well-placed slashes. Thankfully, this seems to be only back in the world of PHP4, so those working with PHP5 should be safe.
</p>]]></description>
      <pubDate>Fri, 25 Sep 2009 10:31:24 -0500</pubDate>
    </item>
  </channel>
</rss>
