<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: WP Directory Traversal Vulnerabilities</title>
	<atom:link href="http://blogsecurity.net/wordpress/wp-directory-traversal-vulnerabilities/feed" rel="self" type="application/rss+xml" />
	<link>http://blogsecurity.net/wordpress/wp-directory-traversal-vulnerabilities</link>
	<description>Always something worth reading...</description>
	<lastBuildDate>Fri, 12 Mar 2010 11:09:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: jonathon</title>
		<link>http://blogsecurity.net/wordpress/wp-directory-traversal-vulnerabilities/comment-page-1#comment-6322</link>
		<dc:creator>jonathon</dc:creator>
		<pubDate>Mon, 07 Jan 2008 18:39:52 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/wp-directory-traversal-vulnerabilities/#comment-6322</guid>
		<description>guess it best to stick with linux for now.</description>
		<content:encoded><![CDATA[<p>guess it best to stick with linux for now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sid</title>
		<link>http://blogsecurity.net/wordpress/wp-directory-traversal-vulnerabilities/comment-page-1#comment-6315</link>
		<dc:creator>sid</dc:creator>
		<pubDate>Sun, 06 Jan 2008 20:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/wp-directory-traversal-vulnerabilities/#comment-6315</guid>
		<description>I did report this to secunia, and they had the same opinion as me.:(</description>
		<content:encoded><![CDATA[<p>I did report this to secunia, and they had the same opinion as me.:(</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DK</title>
		<link>http://blogsecurity.net/wordpress/wp-directory-traversal-vulnerabilities/comment-page-1#comment-6302</link>
		<dc:creator>DK</dc:creator>
		<pubDate>Fri, 04 Jan 2008 09:40:37 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/wp-directory-traversal-vulnerabilities/#comment-6302</guid>
		<description>Alex, looks like Sid didn&#039;t think it was serious enough to mention; however, the problem here is that authenticated users do pose a risk, especially in multi-user blogger projects.</description>
		<content:encoded><![CDATA[<p>Alex, looks like Sid didn&#8217;t think it was serious enough to mention; however, the problem here is that authenticated users do pose a risk, especially in multi-user blogger projects.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alex</title>
		<link>http://blogsecurity.net/wordpress/wp-directory-traversal-vulnerabilities/comment-page-1#comment-6299</link>
		<dc:creator>alex</dc:creator>
		<pubDate>Thu, 03 Jan 2008 22:22:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/wp-directory-traversal-vulnerabilities/#comment-6299</guid>
		<description>Hmm, someone posted about this problem before:
http://www.notsosecure.com/folder2/2007/08/29/yet-another-insecure-wordpress-code/</description>
		<content:encoded><![CDATA[<p>Hmm, someone posted about this problem before:<br />
<a href="http://www.notsosecure.com/folder2/2007/08/29/yet-another-insecure-wordpress-code/" rel="nofollow">http://www.notsosecure.com/folder2/2007/08/29/yet-another-insecure-wordpress-code/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
