<?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"
	>

<channel>
	<title>Kakkoi &#187; 2.3.2</title>
	<atom:link href="http://42.kaizeku.com/taxonomy/232//feed/" rel="self" type="application/rss+xml" />
	<link>http://42.kaizeku.com</link>
	<description>web development, software, windows tips and trick</description>
	<pubDate>Sat, 12 Jul 2008 15:10:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
	<language>en</language>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Upgrade Wordpress 2.3.2</title>
		<link>http://42.kaizeku.com/wordpress/upgrade-wordpress-232/</link>
		<comments>http://42.kaizeku.com/wordpress/upgrade-wordpress-232/#comments</comments>
		<pubDate>Sun, 30 Dec 2007 11:36:40 +0000</pubDate>
		<dc:creator>Noah Ark</dc:creator>
		
		<category><![CDATA[WordPress]]></category>

		<category><![CDATA[vulnerability]]></category>

		<category><![CDATA[2.3.2]]></category>

		<guid isPermaLink="false">http://blog.kakkoi.net/wordpress/upgrade-wordpress-232/</guid>
		<description><![CDATA[WordPress developer had to release this 'securities' fixes before the upcoming 2.4. You could either wait for 2.4 (the milestone is almost ready?) or upgrade immediately. But before others exploit this vulnerability its better to upgrade than sorry. ]]></description>
			<content:encoded><![CDATA[
<!-- google_ad_section_start -->
<p>I just upgrade today, <a href="http://wordpress.org/download/">WordPress 2.3.2</a>, fixed a <a href="http://trac.wordpress.org/ticket/5487">nasty vulnerability</a>. I haven&#8217;t did any test yet but according to &#8220;<a href="http://blog.kakkoi.net/wordpress/upgrade-wordpress-232/#black-domainer">blackhat domainer</a>&#8221; you can view WordPress Draft Entry via simple URL parameters without log in (un-authorize view).<br />
<span id="more-119"></span><br />
WordPress developer had to release this &#8217;securities&#8217; fixes before the upcoming 2.4. You could either wait for 2.4 (the milestone is almost ready?) or upgrade immediately. But before others exploit this vulnerability its better to upgrade. </p>
<p>Peter Westwood&#8217;s sum up all wordpress 2.3.2 recent <a href="http://westi.wordpress.com/2007/12/30/wordpress-232-in-detail/">change and update in details</a>. Read it first before you decide to upgrade.</p>
<h2>External Links</h2>
<ul>
<li><a id="black-domainer" class="url" href="http://www.blackhatdomainer.com/how-to-know-today-what-shoemoney-is-going-to-post-tomorrow/" rel="external">How to know today what ShoeMoney is going to post tomorrow</a></li>
<li><a href="http://wordpress.org/development/2007/12/wordpress-232/">Wordpress 2.3.2 Announcements (dev blog)</a></li>
</ul>
<!-- google_ad_section_end -->
]]></content:encoded>
			<wfw:commentRss>http://42.kaizeku.com/wordpress/upgrade-wordpress-232/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
