<?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: Possible wordpress/server exploit?</title>
	<atom:link href="http://blue-anvil.com/archives/possible-wordpressserver-exploit/feed/" rel="self" type="application/rss+xml" />
	<link>http://blue-anvil.com/archives/possible-wordpressserver-exploit/</link>
	<description>The online blogfolio of Mike Jolley</description>
	<lastBuildDate>Mon, 15 Mar 2010 23:17:57 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Anthony Brewitt</title>
		<link>http://blue-anvil.com/archives/possible-wordpressserver-exploit/comment-page-1/#comment-2966</link>
		<dc:creator>Anthony Brewitt</dc:creator>
		<pubDate>Mon, 20 Oct 2008 11:53:16 +0000</pubDate>
		<guid isPermaLink="false">http://blue-anvil.com/?p=224#comment-2966</guid>
		<description>I have the same problem on a sites running a few different version of WP. Changing file permissions seems to do the trick. Take note: it affects all index.php&#039;s; root index.php, wp-admin/index.php and wp-content/index.php - make all read only!</description>
		<content:encoded><![CDATA[<p>I have the same problem on a sites running a few different version of WP. Changing file permissions seems to do the trick. Take note: it affects all index.php&#8217;s; root index.php, wp-admin/index.php and wp-content/index.php &#8211; make all read only!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://blue-anvil.com/archives/possible-wordpressserver-exploit/comment-page-1/#comment-2964</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Sun, 19 Oct 2008 19:03:32 +0000</pubDate>
		<guid isPermaLink="false">http://blue-anvil.com/?p=224#comment-2964</guid>
		<description>I had a similar problem last month, even though I had the latest WordPress version installed. If you&#039;d view the pages&#039; source, you&#039;d see lines and lines of js, and all google ads would be replaced with po*n &amp; spyware banners.</description>
		<content:encoded><![CDATA[<p>I had a similar problem last month, even though I had the latest WordPress version installed. If you&#8217;d view the pages&#8217; source, you&#8217;d see lines and lines of js, and all google ads would be replaced with po*n &amp; spyware banners.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
