<?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>Code Garage Blog &#187; Plugin Releases</title>
	<atom:link href="http://codegarage.com/blog/category/wordpress/plugin-releases/feed/" rel="self" type="application/rss+xml" />
	<link>http://codegarage.com/blog</link>
	<description></description>
	<lastBuildDate>Tue, 27 Sep 2011 16:39:38 +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>WordPress Timthumb.php Vulnerability Scanner Plugin</title>
		<link>http://codegarage.com/blog/2011/09/wordpress-timthumb-vulnerability-scanner-plugin/</link>
		<comments>http://codegarage.com/blog/2011/09/wordpress-timthumb-vulnerability-scanner-plugin/#comments</comments>
		<pubDate>Fri, 02 Sep 2011 20:20:47 +0000</pubDate>
		<dc:creator>Peter</dc:creator>
				<category><![CDATA[Plugin Releases]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[cleanup]]></category>
		<category><![CDATA[plugin]]></category>
		<category><![CDATA[timthumb]]></category>
		<category><![CDATA[Upgrade]]></category>

		<guid isPermaLink="false">http://codegarage.com/blog/?p=373</guid>
		<description><![CDATA[Over the past few weeks, I&#8217;ve been absolutely inundated with requests to clean up hacks that have exploited the much publicized Timthumb.php vulnerability. I have to assume that the reason most people aren&#8217;t plugging up this security hole on their sites is either They don&#8217;t feel confident in their ability to find the problem They ...]]></description>
			<content:encoded><![CDATA[<p><object width="620" height="349"><param name="movie" value="http://www.youtube.com/v/MFt_XmCMAfI?version=3"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/MFt_XmCMAfI?version=3" type="application/x-shockwave-flash" width="620" height="349" allowscriptaccess="always" allowfullscreen="true"></embed></object></p>
<p>Over the past few weeks, I&#8217;ve been absolutely inundated with requests to clean up hacks that have exploited the much publicized <a href="http://codegarage.com/blog/2011/08/how-to-clean-up-the-timthumb-security-vulnerability/" title="How to Clean Up the TimThumb Security Vulnerability">Timthumb.php vulnerability</a>.  I have to assume that the reason most people aren&#8217;t plugging up this security hole on their sites is either </p>
<ol>
<li>They don&#8217;t feel confident in their ability to find the problem</li>
<li>They feel like the process to fix it is too complicated</li>
</ol>
<p>To combat this, I took a couple of hours this morning to write a plugin that will do the dirty work for you.  The WordPress Timthumb Vulnerability Scanner will check your entire wp-content directory (including all themes, plugins, and uploads) for any vulnerable (pre-2.0) instances of the timthumb script, and give you a one-click upgrade to upgrade each script to the latest, secure version.</p>
<h3>The process is simple:</h3>
<ol>
<li>Download the plugin here:<br />
<a href="http://wordpress.org/extend/plugins/timthumb-vulnerability-scanner/">http://wordpress.org/extend/plugins/timthumb-vulnerability-scanner/</a></li>
<li>Install and activate using either FTP, or the built in WordPress uploader<a href="http://codegarage.com/blog/wp-content/uploads/2011/09/Screen-Shot-2011-09-02-at-2.03.16-PM.png"><img src="http://codegarage.com/blog/wp-content/uploads/2011/09/Screen-Shot-2011-09-02-at-2.03.16-PM-680x484.png" alt="" title="Install the plugin" width="600" height="427" class="aligncenter size-large wp-image-374" /></a></li>
<li>Go to the &#8220;Timthumb Scanner&#8221; page, under the &#8220;Tools&#8221; menu</li>
<li><a href="http://codegarage.com/blog/wp-content/uploads/2011/09/Screen-Shot-2011-09-02-at-2.12.14-PM.png"><img src="http://codegarage.com/blog/wp-content/uploads/2011/09/Screen-Shot-2011-09-02-at-2.12.14-PM-680x484.png" alt="" title="Plugin Page" width="600" height="427" class="aligncenter size-large wp-image-375" /></a><br />
Click the &#8220;Scan&#8221; button.</p>
<li>View your scan results<br />
<a href="http://codegarage.com/blog/wp-content/uploads/2011/09/Screen-Shot-2011-09-02-at-2.14.55-PM.png"><img src="http://codegarage.com/blog/wp-content/uploads/2011/09/Screen-Shot-2011-09-02-at-2.14.55-PM-680x484.png" alt="" title="Screen Shot 2011-09-02 at 2.14.55 PM" width="600" height="427" class="aligncenter size-large wp-image-377" /></a><br />
In this case, I&#8217;ve got one vulnerable (outdated) file, and 2 that have been updated, and are safe.  I&#8217;m going to want to upgrade that one vulnerable file &#8211; to do that, I just need to hit the &#8220;Fix&#8221; button next to it.<br />
You may not have any instances of timthumb on your site, or all of yours may be upgraded &#8211; if so, you&#8217;re all done!</li>
<li>After hitting &#8220;Fix&#8221; for my one problem file, I&#8217;m showing &#8220;No Vulnerabilities Found&#8221;, which means I&#8217;m all set.</li>
</ol>
<p>Just like that, you&#8217;re done.  Quick and painless.</p>
<p>Note: If you&#8217;ve already been hacked, this will NOT clean up your site.  This plugin fixes your door lock &#8211; which doesn&#8217;t matter if the burglars are already in your house.</p>
<p>Let me know of any problems or questions you have in the comments.</p>
<p>Good luck!</p>
<p><strong>EDIT</strong><br />
Looking for a solution to scan a whole server, or a site not running on WordPress?  By sort-of-popular demand, here it is:<br />
<a href="http://codegarage.com/plugins/timthumb-full-server-vulnerability-scanner.zip">http://codegarage.com/plugins/timthumb-full-server-vulnerability-scanner.zip</a><br />
It&#8217;s much less polished, and much less tested, so use at your own risk.</p>
]]></content:encoded>
			<wfw:commentRss>http://codegarage.com/blog/2011/09/wordpress-timthumb-vulnerability-scanner-plugin/feed/</wfw:commentRss>
		<slash:comments>84</slash:comments>
		</item>
		<item>
		<title>New WordPress Plugin:  Default Post Content</title>
		<link>http://codegarage.com/blog/2009/04/new-wordpress-plugin-default-post-content/</link>
		<comments>http://codegarage.com/blog/2009/04/new-wordpress-plugin-default-post-content/#comments</comments>
		<pubDate>Mon, 13 Apr 2009 16:28:06 +0000</pubDate>
		<dc:creator>Peter</dc:creator>
				<category><![CDATA[Admin]]></category>
		<category><![CDATA[Plugin Releases]]></category>
		<category><![CDATA[default post]]></category>
		<category><![CDATA[plugins]]></category>
		<category><![CDATA[post content]]></category>
		<category><![CDATA[Post Meta]]></category>

		<guid isPermaLink="false">http://apartmentonesix.com/?p=144</guid>
		<description><![CDATA[Justin over at justintadlock.com made a post a few days ago about how to preset text in the WordPress post editor.  It&#8217;s a great post, with an interesting filter detailed.  In the comments, somebody mentioned that they&#8217;d like to be able to preset custom fields as well &#8211; something that seems like it shouldn&#8217;t work ...]]></description>
			<content:encoded><![CDATA[<p>Justin over at <a title="Justin Tadlock" href="http://justintadlock.com" target="_blank">justintadlock.com</a> made a post a few days ago about how to <a href="http://justintadlock.com/archives/2009/04/05/how-to-preset-text-in-the-wordpress-post-editor" target="_blank">preset text in the WordPress post editor</a>.  It&#8217;s a great post, with an interesting filter detailed.  In the comments, somebody mentioned that they&#8217;d like to be able to preset custom fields as well &#8211; something that seems like it shouldn&#8217;t work (Custom fields need a post id to work on, and new posts dont have a post id).  Yesterday, the workaround hit me like a slap in the face while I was in the shower &#8211; so I decided to package up this, along with the original code that Justin published in a plugin.</p>
<p>It&#8217;s not the most elegant piece of code in the world, but it works on all the installs I&#8217;ve tried it on.  I&#8217;ll try to put up a post detailing how it works soon, but in the meantime, feel free to download the plugin and give it a try.</p>
<p><a title="Default Post Content Plugin" href="http://yourcodegarage.com/blog/plugins/default-post-content/">Default Post Content Plugin</a></p>
]]></content:encoded>
			<wfw:commentRss>http://codegarage.com/blog/2009/04/new-wordpress-plugin-default-post-content/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
	</channel>
</rss>

