<?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: Matt Cutts Gets Hacked!</title>
	<atom:link href="http://www.pagetrafficbuzz.com/matt-cutts-get-hacked/1554/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pagetrafficbuzz.com/matt-cutts-get-hacked/1554/</link>
	<description>Search engine news, SEO Tips, Google updates, SEO articles</description>
	<lastBuildDate>Wed, 23 May 2012 13:15:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Christopher Buckley&#8230; &#187; Matt Cutts Hacked!</title>
		<link>http://www.pagetrafficbuzz.com/matt-cutts-get-hacked/1554/comment-page-1/#comment-1685</link>
		<dc:creator>Christopher Buckley&#8230; &#187; Matt Cutts Hacked!</dc:creator>
		<pubDate>Sun, 01 Apr 2007 13:38:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.unofficialseoblog.com/2007/04/01/matt-cutts-get-hacked/#comment-1685</guid>
		<description>[...] I&#8217;ve just read that the guys at Unofficial SEO Blog believe that &#8216;Matt&#8217;s upgrade of WordPress installation from 2.0.x to 2.1.x might have helped Dark SEO Team to hack it.&#8217; That&#8217;s depressing if you really think that, guys. This is not wordpress hack, but will be a known exploit for Apache. It will be interesting if the precise exploit is ever detailed. All this demonstrates is why every enterprise site must use some form of application firewall. [...]</description>
		<content:encoded><![CDATA[<p>[...] I&#039;ve just read that the guys at Unofficial SEO Blog believe that &#039;Matt&#039;s upgrade of WordPress installation from 2.0.x to 2.1.x might have helped Dark SEO Team to hack it.&#039; That&#039;s depressing if you really think that, guys. This is not wordpress hack, but will be a known exploit for Apache. It will be interesting if the precise exploit is ever detailed. All this demonstrates is why every enterprise site must use some form of application firewall. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

