<?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.3.2 Released &#8211; Security</title>
	<atom:link href="http://www.solo-technology.com/blog/2007/12/30/wordpress-232-released-security/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.solo-technology.com/blog/2007/12/30/wordpress-232-released-security/</link>
	<description>A Technology Crow in search of Bright Shiny Objects</description>
	<lastBuildDate>Fri, 19 Mar 2010 16:03:27 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Yair</title>
		<link>http://www.solo-technology.com/blog/2007/12/30/wordpress-232-released-security/#comment-31508</link>
		<dc:creator>Yair</dc:creator>
		<pubDate>Mon, 31 Mar 2008 19:01:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.solo-technology.com/blog/2007/12/30/wordpress-232-released-security/#comment-31508</guid>
		<description>during the last few months a few WordPress vulnerabilities were discovered that allowed hackers to inject links into blogs. I find it unbelievable that there is still no solution to this problem.
I heard about the latest wordpress vulnerability from this vulnerability scanner 
http://www.beyondsecurity.com/vulnerability-scanner.html
I guess the only way to learn about new vulnerabilities is to wait for someone else to get hurt and to protect yourself as soon as you get the news.</description>
		<content:encoded><![CDATA[<p>during the last few months a few WordPress vulnerabilities were discovered that allowed hackers to inject links into blogs. I find it unbelievable that there is still no solution to this problem.<br />
I heard about the latest wordpress vulnerability from this vulnerability scanner<br />
<a href="http://www.beyondsecurity.com/vulnerability-scanner.html" rel="nofollow">http://www.beyondsecurity.com/vulnerability-scanner.html</a><br />
I guess the only way to learn about new vulnerabilities is to wait for someone else to get hurt and to protect yourself as soon as you get the news.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Kasten</title>
		<link>http://www.solo-technology.com/blog/2007/12/30/wordpress-232-released-security/#comment-20466</link>
		<dc:creator>Chris Kasten</dc:creator>
		<pubDate>Sun, 30 Dec 2007 19:34:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.solo-technology.com/blog/2007/12/30/wordpress-232-released-security/#comment-20466</guid>
		<description>Oh geeze... ok that makes sense. I guess I didn&#039;t think it all the way through.

Thanks for stopping by and clarifying :-)</description>
		<content:encoded><![CDATA[<p>Oh geeze&#8230; ok that makes sense. I guess I didn&#8217;t think it all the way through.</p>
<p>Thanks for stopping by and clarifying <img src='http://www.solo-technology.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Westwood</title>
		<link>http://www.solo-technology.com/blog/2007/12/30/wordpress-232-released-security/#comment-20462</link>
		<dc:creator>Peter Westwood</dc:creator>
		<pubDate>Sun, 30 Dec 2007 19:20:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.solo-technology.com/blog/2007/12/30/wordpress-232-released-security/#comment-20462</guid>
		<description>The custom database error page can&#039;t be theme specific [because] WordPress needs database access in order to know what the current theme is.</description>
		<content:encoded><![CDATA[<p>The custom database error page can&#8217;t be theme specific [because] WordPress needs database access in order to know what the current theme is.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
