<?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>Mommy Blogger .me &#187; Security</title>
	<atom:link href="http://www.mommyblogger.me/tag/security/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mommyblogger.me</link>
	<description>It&#039;s Not Just a Boys&#039; Club Anymore</description>
	<lastBuildDate>Mon, 11 Apr 2011 23:41:37 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>WordPress 3.0.2 Released- Upgrade Now!</title>
		<link>http://www.mommyblogger.me/wordpress-how-to-upgrade-to-new-version/</link>
		<comments>http://www.mommyblogger.me/wordpress-how-to-upgrade-to-new-version/#comments</comments>
		<pubDate>Sat, 04 Dec 2010 15:07:00 +0000</pubDate>
		<dc:creator>Danelle Ice - Mommy Blogger Me</dc:creator>
				<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://www.mommyblogger.me/wordpress-how-to-upgrade-to-new-version/</guid>
		<description><![CDATA[Calling all bloggers running WordPress as their content management system (CMS) – yes, I’m talking about you guys and gals with self-hosted WordPress installations.&#160; WordPress version 3.0.2 just came out (release date 11/30/10) and if you haven’t done so already, it’s time to upgrade your WordPress installation. WordPress 3.0.2 is a mandatory security update, which [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.mommyblogger.me%2Fwordpress-how-to-upgrade-to-new-version%2F" onclick="urchinTracker('/outgoing/api.tweetmeme.com/share?url=http_3A_2F_2Fwww.mommyblogger.me_2Fwordpress-how-to-upgrade-to-new-version_2F&amp;referer=');"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.mommyblogger.me%2Fwordpress-how-to-upgrade-to-new-version%2F&amp;source=HomeEverAfter&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" title="WordPress 3.0.2 Released  Upgrade Now!" alt=" WordPress 3.0.2 Released  Upgrade Now!" /><br />
			</a>
		</div>
<p><a href="http://mommyblogger.me/wp-content/uploads/2010/12/image.png" onclick="urchinTracker('/outgoing/mommyblogger.me/wp-content/uploads/2010/12/image.png?referer=');"><img title="image" style="border-right: 0px; padding-right: 0px; border-top: 0px; display: inline; padding-left: 0px; float: left; background-image: none; margin: 0px 20px 10px 0px; border-left: 0px; padding-top: 0px; border-bottom: 0px" height="115" alt="image thumb WordPress 3.0.2 Released  Upgrade Now!" src="http://mommyblogger.me/wp-content/uploads/2010/12/image_thumb.png" width="100" align="left" border="0" /></a>Calling all bloggers running WordPress as their content management system (CMS) – yes, I’m talking about you guys and gals with self-hosted WordPress installations.&nbsp; WordPress version 3.0.2 just came out (release date 11/30/10) and if you haven’t done so already, it’s time to upgrade your WordPress installation.</p>
<p>WordPress 3.0.2 is a mandatory security update, which means if you know what’s good for the safety of your blog, you’ll get on this update right away!</p>
<h2>How to Upgrade to WordPress 3.0.2</h2>
<p>To upgrade your WordPress installation to version 3.0.2, you have several choices:</p>
<p>1. You can <a title="follow the directions at the WordPress Codex here" href="http://codex.wordpress.org/Version_3.0.2" target="_blank" onclick="urchinTracker('/outgoing/codex.wordpress.org/Version_3.0.2?referer=');">follow the directions at the WordPress Codex here</a>.</p>
<p>2.&nbsp; Log in to your WordPress dashboard and you’ll get a message at the top of the page alerting you to the new version. It also has a link to the download information.</p>
<p>3.&nbsp; <a title="Download the plugin WordPress Automatic Upgrade" href="http://wordpress.org/extend/plugins/wordpress-automatic-upgrade/" target="_blank" onclick="urchinTracker('/outgoing/wordpress.org/extend/plugins/wordpress-automatic-upgrade/?referer=');">Download the plugin WordPress Automatic Upgrade</a>, which will guide you through a series of clicks in your dashboard to update to the new version.&nbsp; This handy plugin is, by far, the easiest way to upgrade your WordPress.</p>
<h2>List of the Changes Made in WordPress 3.0.2</h2>
<p>From the WordPress.org site, the following changes were made in this security update:</p>
<ul>
<ul>
<li>“Fix moderate security issue where a malicious Author-level user could gain further access to the site. (<a href="http://core.trac.wordpress.org/changeset/16625" onclick="urchinTracker('/outgoing/core.trac.wordpress.org/changeset/16625?referer=');">r16625</a>) </li>
<li>Remove pingback/trackback blogroll whitelisting feature as it can easily be abused. (<a href="http://core.trac.wordpress.org/ticket/13887" onclick="urchinTracker('/outgoing/core.trac.wordpress.org/ticket/13887?referer=');">#13887</a>)
<li>Fix canonical redirection for permalinks containing %category% with nested categories and paging. (<a href="http://core.trac.wordpress.org/ticket/13471" onclick="urchinTracker('/outgoing/core.trac.wordpress.org/ticket/13471?referer=');">#13471</a>)
<li>Fix occasional irrelevant error messages on plugin activation. (<a href="http://core.trac.wordpress.org/ticket/15062" onclick="urchinTracker('/outgoing/core.trac.wordpress.org/ticket/15062?referer=');">#15062</a>)
<li>Minor XSS fixes in request_filesystem_credentials() and when deleting a plugin. (<a href="http://core.trac.wordpress.org/changeset/16367" onclick="urchinTracker('/outgoing/core.trac.wordpress.org/changeset/16367?referer=');">r16367</a>, <a href="http://core.trac.wordpress.org/changeset/16373" onclick="urchinTracker('/outgoing/core.trac.wordpress.org/changeset/16373?referer=');">r16373</a>)
<li>Clarify the license in the readme (<a href="http://core.trac.wordpress.org/changeset/15534" onclick="urchinTracker('/outgoing/core.trac.wordpress.org/changeset/15534?referer=');">r15534</a>)
<li>Multisite: Fix the delete_user meta capability (<a href="http://core.trac.wordpress.org/changeset/15562" onclick="urchinTracker('/outgoing/core.trac.wordpress.org/changeset/15562?referer=');">r15562</a>)
<li>Multisite: Force current_user_can_for_blog() to run map_meta_cap() even for super admins (<a href="http://core.trac.wordpress.org/ticket/15122" onclick="urchinTracker('/outgoing/core.trac.wordpress.org/ticket/15122?referer=');">#15122</a>)
<li>Multisite: Fix ms-files.php content type headers when requesting a URL with a query string (<a href="http://core.trac.wordpress.org/ticket/14450" onclick="urchinTracker('/outgoing/core.trac.wordpress.org/ticket/14450?referer=');">#14450</a>)
<li>Multisite: Fix the usage of the SUBDOMAIN_INSTALL constant for upgraded WordPress MU installs (<a href="http://core.trac.wordpress.org/ticket/14536" onclick="urchinTracker('/outgoing/core.trac.wordpress.org/ticket/14536?referer=');">#14536</a>) “</li>
</ul>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.mommyblogger.me/wordpress-how-to-upgrade-to-new-version/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress 2.8.4 Upgrade &#8211; Security Must</title>
		<link>http://www.mommyblogger.me/wordpress-2-8-4-upgrade-security-must/</link>
		<comments>http://www.mommyblogger.me/wordpress-2-8-4-upgrade-security-must/#comments</comments>
		<pubDate>Thu, 13 Aug 2009 22:49:00 +0000</pubDate>
		<dc:creator>Danelle Ice - Mommy Blogger Me</dc:creator>
				<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[CMS]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Upgrades]]></category>

		<guid isPermaLink="false">http://www.mommyblogger.me/wordpress-2-8-4-upgrade-security-must/</guid>
		<description><![CDATA[There was a security vulnerability found in the previous Wordpress version that allowed people to use a special URL that could bypass the security for password resets. You can upgrade to Wordpress 2.8.4 from your dashboard or download the latest version here.]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.mommyblogger.me%2Fwordpress-2-8-4-upgrade-security-must%2F" onclick="urchinTracker('/outgoing/api.tweetmeme.com/share?url=http_3A_2F_2Fwww.mommyblogger.me_2Fwordpress-2-8-4-upgrade-security-must_2F&amp;referer=');"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.mommyblogger.me%2Fwordpress-2-8-4-upgrade-security-must%2F&amp;source=HomeEverAfter&amp;style=normal&amp;service=bit.ly&amp;b=2" height="61" width="50" title="Wordpress 2.8.4 Upgrade &ndash; Security Must" alt=" Wordpress 2.8.4 Upgrade &ndash; Security Must" /><br />
			</a>
		</div>
<p><strong>WordPress 2.8.4</strong> was released yesterday (August 12, 2009) and if you haven’t upgraded your blog yet, you should do so ASAP.&nbsp; You can <strong>upgrade to WordPress 2.8.4</strong> from your dashboard or <a title="download the latest version here" href="http://wordpress.org/download/" target="_blank" onclick="urchinTracker('/outgoing/wordpress.org/download/?referer=');">download the latest version here</a>.</p>
<p>There was a security vulnerability found in the previous WordPress version that allowed people to use a special URL that could bypass the security for password resets.&nbsp; In essence, this would enable a hacker to hit user accounts (like the admin account), reset your password, and have access to your blog.</p>
<p><span id="more-2573"></span>
<p>Think it couldn’t happen to your blog?&nbsp; It can – <a title="Robert Scoble&rsquo;s" href="http://scobleizer.com/" target="_blank" onclick="urchinTracker('/outgoing/scobleizer.com/?referer=');">Robert Scoble’s</a> site was hacked into yesterday.&nbsp; Don’t let this happen to you!</p>
<p><img title="image" style="border-right: 0px; border-top: 0px; display: inline; margin: 0px 20px 0px 0px; border-left: 0px; border-bottom: 0px" height="162" alt="image Wordpress 2.8.4 Upgrade &ndash; Security Must" src="http://mommyblogger.me/wp-content/uploads/2009/08/image.png" width="246" align="left" border="0" /></p>
<p>We luckily upgraded all of our WordPress sites when the release was announced and haven’t had any problems.&nbsp; </p>
<h2>Security Not a Drawback to Using WordPress</h2>
<p>Some people use security issues like yesterday’s as an excuse to not use WordPress.&nbsp; However, the window is very small between the time hackers discover a vulnerability and WordPress finds out about it and creates a solidly tested solution.&nbsp; The power of using an open source CMS with such collective knowledge going into its development really gives WordPress users the blogging edge, with an extremely robust platform.&nbsp; </p>
<p>To put it plainly, there is no better than WordPress, so don’t let yesterday’s security issue scare you away.</p>
<p>Remember that WordPress updates are critical for your security and should be installed as soon as you know about them.&nbsp; You can keep informed of these updates by simply checking your WordPress dashboard or following the <a title="Wordpress Blog" href="http://wordpress.org/development/2009/08/2-8-4-security-release/" target="_blank" onclick="urchinTracker('/outgoing/wordpress.org/development/2009/08/2-8-4-security-release/?referer=');">WordPress Blog</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mommyblogger.me/wordpress-2-8-4-upgrade-security-must/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

