<?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 2.0.6 is Out</title>
	<atom:link href="http://www.bloggingpro.com/archives/2007/01/05/wordpress-206-is-out/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bloggingpro.com/archives/2007/01/05/wordpress-206-is-out/</link>
	<description>News, plugins and themes for blogging applications</description>
	<lastBuildDate>Thu, 09 Feb 2012 19:29:02 +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: Mark Marucot</title>
		<link>http://www.bloggingpro.com/archives/2007/01/05/wordpress-206-is-out/#comment-108616</link>
		<dc:creator>Mark Marucot</dc:creator>
		<pubDate>Sun, 07 Jan 2007 23:53:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2007/01/05/wordpress-206-is-out/#comment-108616</guid>
		<description>Wordpress 2.0.6 is released which includes security fix about the persistent XSS vulnerability. This security issue has been found in specifically on Wordpress 2.0.5&#039;s template.php allows a user with access to the templates.php to insert arbitrary HTML and/or Javascript which can be then executed by other administrators. The link title of recent accessed files is not sanitized which causes the HTML tags ending with &quot;/&quot; fail. Prior to 2.0.6 release, the temporary workaround is using open &quot;IMG&quot; tags which only works on Firefox and Internet Explorer</description>
		<content:encoded><![CDATA[<p>WordPress 2.0.6 is released which includes security fix about the persistent XSS vulnerability. This security issue has been found in specifically on WordPress 2.0.5&#8242;s template.php allows a user with access to the templates.php to insert arbitrary HTML and/or Javascript which can be then executed by other administrators. The link title of recent accessed files is not sanitized which causes the HTML tags ending with &#8220;/&#8221; fail. Prior to 2.0.6 release, the temporary workaround is using open &#8220;IMG&#8221; tags which only works on Firefox and Internet Explorer</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ThÃ¡ssius Veloso</title>
		<link>http://www.bloggingpro.com/archives/2007/01/05/wordpress-206-is-out/#comment-108510</link>
		<dc:creator>ThÃ¡ssius Veloso</dc:creator>
		<pubDate>Sat, 06 Jan 2007 20:35:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2007/01/05/wordpress-206-is-out/#comment-108510</guid>
		<description>I was just reading about the release and it seems the former version to be dangerous. But DreamHost hasn&#039;t already allowed the one-click update. So, I&#039;ll have to wait more.</description>
		<content:encoded><![CDATA[<p>I was just reading about the release and it seems the former version to be dangerous. But DreamHost hasn&#8217;t already allowed the one-click update. So, I&#8217;ll have to wait more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron</title>
		<link>http://www.bloggingpro.com/archives/2007/01/05/wordpress-206-is-out/#comment-108444</link>
		<dc:creator>Ron</dc:creator>
		<pubDate>Fri, 05 Jan 2007 22:37:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2007/01/05/wordpress-206-is-out/#comment-108444</guid>
		<description>Works like charm!</description>
		<content:encoded><![CDATA[<p>Works like charm!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

