<?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>Weblog Tools Collection &#187; exploit</title>
	<atom:link href="http://weblogtoolscollection.com/archives/tag/exploit/feed/" rel="self" type="application/rss+xml" />
	<link>http://weblogtoolscollection.com</link>
	<description>Weblog Tools Blogging Tools Blog</description>
	<lastBuildDate>Tue, 14 Feb 2012 14:00:48 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>WordPress Search Based DOS Attack</title>
		<link>http://weblogtoolscollection.com/archives/2010/01/01/wordpress-search-based-dos-attack/</link>
		<comments>http://weblogtoolscollection.com/archives/2010/01/01/wordpress-search-based-dos-attack/#comments</comments>
		<pubDate>Fri, 01 Jan 2010 20:23:13 +0000</pubDate>
		<dc:creator>Jeff Chandler</dc:creator>
				<category><![CDATA[WordPress Security]]></category>
		<category><![CDATA[attack]]></category>
		<category><![CDATA[dos]]></category>
		<category><![CDATA[exploit]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://weblogtoolscollection.com/?p=7462</guid>
		<description><![CDATA[I was notified on Twitter the other day that there was a new 0 Day denial of service exploit for WordPress. When asking on Twitter if it worked, numerous people replied that the published code did work and was taking down their sites. This raised some red flags for me so I jumped into the WordPress-Dev IRC channel to figure out what was going on. The way this denial of service attack works is that a random search string is sent to the search form of a WordPress based website. Caching plugins do not work against this because the search string is randomized. It&#8217;s quite simple but what I&#8217;ve been told is that this is not an issue for WordPress to handle. Instead, this attack should be dealt with by the webhost on a firewall level. At one point, a ticket was created by Scribu but has since been closed [...]]]></description>
			<content:encoded><![CDATA[<p>I was notified on Twitter the other day that there was a new 0 Day denial of service exploit for WordPress. When asking on Twitter if it worked, numerous people replied that the published code did work and was taking down their sites. This raised some red flags for me so I jumped into the WordPress-Dev IRC channel to figure out what was going on.</p>
<p>The way this denial of service attack works is that a random search string is sent to the search form of a WordPress based website. Caching plugins do not work against this because the search string is randomized. It&#8217;s quite simple but what I&#8217;ve been told is that this is not an issue for WordPress to handle. Instead, this attack should be dealt with by the webhost on a firewall level. At one point, <a href="http://core.trac.wordpress.org/ticket/11685" target="_blank">a ticket was created</a> by Scribu but has since been closed as won&#8217;t fix.</p>
<p>So at the end of the day, the best defense you have is a competent webhost that will do their part to prevent these attacks from happening. No reason to be alarmed. </p>
]]></content:encoded>
			<wfw:commentRss>http://weblogtoolscollection.com/archives/2010/01/01/wordpress-search-based-dos-attack/feed/</wfw:commentRss>
		<slash:comments>27</slash:comments>
		</item>
		<item>
		<title>Comment Remix Security Bulletin</title>
		<link>http://weblogtoolscollection.com/archives/2008/11/01/comment-remix-security-bulletin/</link>
		<comments>http://weblogtoolscollection.com/archives/2008/11/01/comment-remix-security-bulletin/#comments</comments>
		<pubDate>Sun, 02 Nov 2008 00:22:49 +0000</pubDate>
		<dc:creator>Jeff Chandler</dc:creator>
				<category><![CDATA[WordPress Plugins]]></category>
		<category><![CDATA[WordPress Security]]></category>
		<category><![CDATA[bulletin]]></category>
		<category><![CDATA[comment remix]]></category>
		<category><![CDATA[exploit]]></category>
		<category><![CDATA[plugins]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://weblogtoolscollection.com/?p=4486</guid>
		<description><![CDATA[Normally, we usually keep a maximum of two posts a day that are published on WeblogTooolsCollection as a means of keeping your dashboard from being overcome by us. However, considering that the following security bulletin has been published concerning the plugin (WP Comment Remix) and it won the WeblogToolsCollection plugin competition, I felt it was important to pass along this security bulletin to you. According to the bulletin that was published by Chxsecurity.org version 1.4.3 contains the following vulnerabilities: SQL Injection: caused by unsanitized variable “p” in the ajax_comments.php file. Cross Site Scripting: This affects authenticated and unauthenticated users. Cross Site Request Forgery: the form generated through wpcr_do_options_page lacks the WordPress wp_nonce security function. These vulnerabilities are considered HIGH risks however, the latest version (1.4.4) apparently addresses these issues. If you are using this plugin on your blog, be sure to upgrade it to the latest version.]]></description>
			<content:encoded><![CDATA[<p>Normally, we usually keep a maximum of two posts a day that are published on WeblogTooolsCollection as a means of keeping your dashboard from being overcome by us. However, considering that the following security bulletin has been published concerning the plugin (<a href="http://pressography.com/plugins/wp-comment-remix/" target="_blank">WP Comment Remix</a>) and it won the <a href="http://weblogtoolscollection.com/pluginblog/" target="_blank">WeblogToolsCollection plugin competition</a>, I felt it was important to pass along <a href="http://blogsecurity.net/wordpress/multiple-vulnerabilities-in-wp-comment-remix-143/" target="_blank">this security bulletin</a> to you.</p>
<p>According to the bulletin that was published by <a href="http://chxsecurity.org/advisories/adv-3-full.txt" target="_blank">Chxsecurity.org</a> version 1.4.3 contains the following vulnerabilities:</p>
<ul>
<li>SQL Injection: caused by unsanitized variable “p” in the ajax_comments.php file.</li>
<li>Cross Site Scripting: This affects authenticated and unauthenticated users.</li>
<li>Cross Site Request Forgery: the form generated through wpcr_do_options_page lacks the WordPress wp_nonce security function.</li>
</ul>
<p>These vulnerabilities are considered HIGH risks however, the latest version (1.4.4) apparently addresses these issues. If you are using this plugin on your blog, be sure to upgrade it to the latest version.</p>
]]></content:encoded>
			<wfw:commentRss>http://weblogtoolscollection.com/archives/2008/11/01/comment-remix-security-bulletin/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Vulnerable WordPress Blogs Not Being Indexed</title>
		<link>http://weblogtoolscollection.com/archives/2008/04/08/vulnerable-wordpress-blogs-not-being-indexed/</link>
		<comments>http://weblogtoolscollection.com/archives/2008/04/08/vulnerable-wordpress-blogs-not-being-indexed/#comments</comments>
		<pubDate>Tue, 08 Apr 2008 14:26:38 +0000</pubDate>
		<dc:creator>Mark Ghosh</dc:creator>
				<category><![CDATA[Business of Blogging]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[WordPress Security]]></category>
		<category><![CDATA[exploit]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[wordpress-2.5]]></category>

		<guid isPermaLink="false">http://weblogtoolscollection.com/?p=3401</guid>
		<description><![CDATA[Vulnerable WordPress Blogs Not Being Indexed: Technorati has decided to not index vulnerable and exploited WordPress blogs. This comes after the recent spat of hacks that were discovered on various high profile blogs and websites. What was even more interesting was the fact that some of these hacks and exploitations might have come from covert and encrypted code hidden in various themes available for free over the web. The moral of this story is that you need to upgrade your WordPress blog now to WordPress 2.5. Just so that everyone is aware, WordPress 2.5 is the latest stable version and this should be the version that everyone should upgrade to. Any older versions leaves you vulnerable. [EDIT] As mentioned on the legacy 2.0 page, WordPress 2.0.11 is the latest stable download with all the latest security fixes for the 2.0 branch. However, WordPress 2.5 is still the latest and the [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://technorati.com/weblog/2008/04/424.html">Vulnerable WordPress Blogs Not Being Indexed</a>: Technorati has decided to not index vulnerable and exploited WordPress blogs. This comes after the <a href="http://www.blogherald.com/2008/04/08/technorati-no-longer-indexing-hacked-or-vulnerable-wordpress-blogs/">recent spat of hacks</a> that were discovered on <a href="http://www.deepjiveinterests.com/2008/04/07/breaking-tailrank-exposes-massive-number-of-blogs-hacked/">various high profile blogs and websites</a>. What was even more interesting was the fact that <a href="http://gigaom.com/2008/04/07/blog-hacks-coming-back-to-roost/">some of these hacks and exploitations</a> might have come from <a href="http://www.yugatech.com/blog/blogosphere/massive-blog-hackery-exposed/">covert and encrypted code hidden in various themes available for free over the web</a>. The moral of this story is that you need to upgrade your WordPress blog now to WordPress 2.5.</p>
<p>Just so that everyone is aware, WordPress 2.5 is the latest stable version and this should be the version that everyone should upgrade to. <span style="text-decoration: line-through;">Any older versions leaves you vulnerable</span>. [EDIT] As mentioned on the <a href="http://wordpress.org/download/legacy/">legacy 2.0 page</a>, WordPress 2.0.11 is the latest stable download with all the latest security fixes for the 2.0 branch. However, WordPress 2.5 is still the latest and the greatest and should be everyones upgrade target.</p>
<p>As for themes, if you feel that the theme you are using might be suspect of something strange, just disable it and get something else. I suggest you download themes from the original author&#8217;s website/blog and stay away from any theme that has an encrypted footer (though that would be hard to determine without looking at the code). At weblogtoolscollection.com we try our darnest to link directly to theme authors for the download.</p>
<p>Technorati is just the beginning. If your blog has spammy links, has covert hidden pages or links, is used for nefarious purposes, even without your knowledge, you are being penalized by the search engines. We are going to put together a post on how to figure out if your blog is hacked/exploited, clean up your blog if it <em>is</em> hacked, get your blog back to order, find spammy pages if they do exist and how to get your blog re-indexed. In the meantime, if you know of a good resource, please let us know and we will add it to the post.</p>
<p>Today is a good day to upgrade to <a href="http://wordpress.org/download/">WordPress 2.5</a></p>
]]></content:encoded>
			<wfw:commentRss>http://weblogtoolscollection.com/archives/2008/04/08/vulnerable-wordpress-blogs-not-being-indexed/feed/</wfw:commentRss>
		<slash:comments>57</slash:comments>
		</item>
	</channel>
</rss>
<!-- This Quick Cache file was built for (  weblogtoolscollection.com/archives/tag/exploit/feed/ ) in 0.89994 seconds, on Feb 14th, 2012 at 6:05 pm UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 14th, 2012 at 7:05 pm UTC -->
