<?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: Security Vulnerability In WordPress</title>
	<atom:link href="http://www.bloggingpro.com/archives/2005/05/27/security-vulnerability-in-wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bloggingpro.com/archives/2005/05/27/security-vulnerability-in-wordpress/</link>
	<description>News, plugins and themes for blogging applications</description>
	<lastBuildDate>Mon, 22 Mar 2010 13:50:21 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mind Sharer - For The Marketing Mind &#187; Wordpress 1.5.1.2 on fixing security vulnerability</title>
		<link>http://www.bloggingpro.com/archives/2005/05/27/security-vulnerability-in-wordpress/comment-page-1/#comment-9065</link>
		<dc:creator>Mind Sharer - For The Marketing Mind &#187; Wordpress 1.5.1.2 on fixing security vulnerability</dc:creator>
		<pubDate>Sat, 28 May 2005 12:14:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2005/05/27/security-vulnerability-in-wordpress/#comment-9065</guid>
		<description>[...] erwriting your old 1.5 files. 	Wordpress Security Update - [Wordpress development blog via Blogging Pro]                                           [...]</description>
		<content:encoded><![CDATA[<p>[...] erwriting your old 1.5 files. 	Wordpress Security Update &#8211; [Wordpress development blog via Blogging Pro]                 </p>
<p>     [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mind Sharer - For The Marketing Mind &#187; Wordpress 1.5.1.2 on fixing security vulnerability</title>
		<link>http://www.bloggingpro.com/archives/2005/05/27/security-vulnerability-in-wordpress/comment-page-1/#comment-9064</link>
		<dc:creator>Mind Sharer - For The Marketing Mind &#187; Wordpress 1.5.1.2 on fixing security vulnerability</dc:creator>
		<pubDate>Sat, 28 May 2005 12:14:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2005/05/27/security-vulnerability-in-wordpress/#comment-9064</guid>
		<description>[...] erwriting your old 1.5 files. 	Wordpress Security Update - [Wordpress development blog via Blogging Pro]                                           [...]</description>
		<content:encoded><![CDATA[<p>[...] erwriting your old 1.5 files. 	Wordpress Security Update &#8211; [Wordpress development blog via Blogging Pro]                 </p>
<p>     [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HTNet</title>
		<link>http://www.bloggingpro.com/archives/2005/05/27/security-vulnerability-in-wordpress/comment-page-1/#comment-9063</link>
		<dc:creator>HTNet</dc:creator>
		<pubDate>Sat, 28 May 2005 01:49:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2005/05/27/security-vulnerability-in-wordpress/#comment-9063</guid>
		<description>&lt;strong&gt;WordPress Security Update&lt;/strong&gt;

	There&#8217;s a security update for WP. More info can be read here (WP Dev Blog) and on Blogging Pro.
	Basically you just need to insert one line in /wp-includes/template-functions-category.php, somewhere after line 130:
	function get_the_category_by_...</description>
		<content:encoded><![CDATA[<p><strong>WordPress Security Update</strong></p>
<p>	There&#8217;s a security update for WP. More info can be read here (WP Dev Blog) and on Blogging Pro.<br />
	Basically you just need to insert one line in /wp-includes/template-functions-category.php, somewhere after line 130:<br />
	function get_the_category_by_&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
