<?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>Traveling Project &#187; wordpress exploit</title>
	<atom:link href="http://www.travelingproject.com/tag/wordpress-exploit/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.travelingproject.com</link>
	<description>Blogging to Make Money for Traveling!</description>
	<lastBuildDate>Thu, 22 Dec 2011 14:48:36 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Traveling Project Hit by Recent WordPress Exploit</title>
		<link>http://www.travelingproject.com/2009/traveling-project-hit-by-recent-wordpress-exploit/</link>
		<comments>http://www.travelingproject.com/2009/traveling-project-hit-by-recent-wordpress-exploit/#comments</comments>
		<pubDate>Wed, 09 Sep 2009 19:33:17 +0000</pubDate>
		<dc:creator>TravelDude</dc:creator>
				<category><![CDATA[Miscellaneous Ramblings]]></category>
		<category><![CDATA[wordpress bug]]></category>
		<category><![CDATA[wordpress exploit]]></category>

		<guid isPermaLink="false">http://www.travelingproject.com/?p=63</guid>
		<description><![CDATA[Every blogger probably knows about the recent WordPress exploit which was pretty big news.  Well, because I didn&#8217;t upgrade my WordPress installation right away Traveling Project actually fell victim to the exploit.  How did I know? When I went to the &#8220;Users&#8221; section of the Admin Panel I noticed that it said there were two [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: center;"><img class="size-full wp-image-64 aligncenter" title="Wordpress" src="http://www.travelingproject.com/wp-content/uploads/2009/09/wordpress-logo.png" alt="Wordpress" width="320" height="320" /></p>
<p>Every blogger probably knows about the recent WordPress exploit which was pretty big news.  Well, because I didn&#8217;t upgrade my WordPress installation right away Traveling Project actually fell victim to the exploit.  How did I know?</p>
<p>When I went to the &#8220;Users&#8221; section of the Admin Panel I noticed that it said there were two administrators for the blog.  When I checked the list it only showed my administrator account designated as an &#8220;admin&#8221;.  This was one of the symptoms of the exploit so I knew the blog had been hit.</p>
<p>To fix the exploit I went into the MySQL database for Traveling Project and checked the &#8220;Users&#8221; table in the database.  I compared the list of users in the table to the list of users in the Admin Panel and deleted the only user not showing in the Admin Panel.  When I refreshed the Admin Panel it changed from showing two admin users to only one admin user, so I knew that user was the culprit and the issue was fixed.  I then updated my WordPress installation to the latest version and changed my admin password just in case.  Luckily there wasn&#8217;t any other damage or changes done to Traveling Project.  I still have to go through the old posts and rest of the blog to double check everything though.</p>
<p>So for anyone running WordPress this is just a friendly reminder to update your installations to the latest version!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.travelingproject.com/2009/traveling-project-hit-by-recent-wordpress-exploit/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

