<?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: WordPress Under Attack: Reason to Upgrade to 2.8.4</title>
	<atom:link href="http://www.blogherald.com/2009/09/06/wordpress-org-under-attack-reason-to-upgrade-to-2-8-4/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.blogherald.com/2009/09/06/wordpress-org-under-attack-reason-to-upgrade-to-2-8-4/</link>
	<description>The leading source of news covering social media and the blogosphere.</description>
	<lastBuildDate>Mon, 13 Feb 2012 09:18:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Jamie Allsop</title>
		<link>http://www.blogherald.com/2009/09/06/wordpress-org-under-attack-reason-to-upgrade-to-2-8-4/comment-page-1/#comment-1104886</link>
		<dc:creator>Jamie Allsop</dc:creator>
		<pubDate>Wed, 09 Sep 2009 08:17:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/?p=14202#comment-1104886</guid>
		<description>As soon as I found out about this issue I updated straight away.</description>
		<content:encoded><![CDATA[<p>As soon as I found out about this issue I updated straight away.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jayce</title>
		<link>http://www.blogherald.com/2009/09/06/wordpress-org-under-attack-reason-to-upgrade-to-2-8-4/comment-page-1/#comment-1104881</link>
		<dc:creator>Jayce</dc:creator>
		<pubDate>Wed, 09 Sep 2009 02:56:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/?p=14202#comment-1104881</guid>
		<description>I updated immediately after seeing this issue. ;)</description>
		<content:encoded><![CDATA[<p>I updated immediately after seeing this issue. ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://www.blogherald.com/2009/09/06/wordpress-org-under-attack-reason-to-upgrade-to-2-8-4/comment-page-1/#comment-1104847</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Sun, 06 Sep 2009 11:21:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/?p=14202#comment-1104847</guid>
		<description>I upgraded to 2.8.4 as soon as it came out, but this past week I got e-mail notifications of several &quot;new users.&quot; I became immediately suspicious, especially since I have no link available whereby the public can sign up to be a user ... there&#039;s no need to be registered as a user on my blog since anyone can read it and all comments are moderated. So I unchecked &quot;Anyone can register&quot; in the General Settings, deleted all users except my wife and me, and changed the password.

I&#039;m hoping I am now safe. I see no other signs of anything odd, but then I don&#039;t know enough about WordPress.org code and databases to get into the bowels of the thing to know if anything else is going on. I guess I&#039;ll just wait and hold my breath?</description>
		<content:encoded><![CDATA[<p>I upgraded to 2.8.4 as soon as it came out, but this past week I got e-mail notifications of several &#8220;new users.&#8221; I became immediately suspicious, especially since I have no link available whereby the public can sign up to be a user &#8230; there&#8217;s no need to be registered as a user on my blog since anyone can read it and all comments are moderated. So I unchecked &#8220;Anyone can register&#8221; in the General Settings, deleted all users except my wife and me, and changed the password.</p>
<p>I&#8217;m hoping I am now safe. I see no other signs of anything odd, but then I don&#8217;t know enough about WordPress.org code and databases to get into the bowels of the thing to know if anything else is going on. I guess I&#8217;ll just wait and hold my breath?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

