<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: New Wordpress 2.3.3 Exploit/Vulnerability &#8211; Adds Spam Directory /wp-content/1/</title>
	<atom:link href="http://smackdown.blogsblogsblogs.com/2008/03/23/new-wordpress-233-exploitvulnerability-adds-spam-directory-wp-content1/feed/" rel="self" type="application/rss+xml" />
	<link>http://smackdown.blogsblogsblogs.com/2008/03/23/new-wordpress-233-exploitvulnerability-adds-spam-directory-wp-content1/</link>
	<description>Smackdown!</description>
	<lastBuildDate>Mon, 15 Mar 2010 20:42:03 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nova vulnerabilitat a Wordpress 2.3.3</title>
		<link>http://smackdown.blogsblogsblogs.com/2008/03/23/new-wordpress-233-exploitvulnerability-adds-spam-directory-wp-content1/comment-page-2/#comment-17890</link>
		<dc:creator>Nova vulnerabilitat a Wordpress 2.3.3</dc:creator>
		<pubDate>Mon, 11 May 2009 20:07:40 +0000</pubDate>
		<guid isPermaLink="false">http://smackdown.blogsblogsblogs.com/2008/03/23/new-wordpress-233-exploitvulnerability-adds-spam-directory-wp-content1/#comment-17890</guid>
		<description>[...]  Hola! Si ets nou aquí, pot ser que vulguis subscriure&#039;t al feed RSS.S&#8217;ha descobert una nova vulnerabilitat que a Wordpress 2.3.3 que deixa el nostre blog vulnerable a atacs de injecció de codi; amb aquesta tècnica, els [...]</description>
		<content:encoded><![CDATA[<p>[...]  Hola! Si ets nou aquí, pot ser que vulguis subscriure&#8217;t al feed RSS.S&#8217;ha descobert una nova vulnerabilitat que a Wordpress 2.3.3 que deixa el nostre blog vulnerable a atacs de injecció de codi; amb aquesta tècnica, els [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SEO Directory</title>
		<link>http://smackdown.blogsblogsblogs.com/2008/03/23/new-wordpress-233-exploitvulnerability-adds-spam-directory-wp-content1/comment-page-2/#comment-14213</link>
		<dc:creator>SEO Directory</dc:creator>
		<pubDate>Tue, 24 Mar 2009 13:48:40 +0000</pubDate>
		<guid isPermaLink="false">http://smackdown.blogsblogsblogs.com/2008/03/23/new-wordpress-233-exploitvulnerability-adds-spam-directory-wp-content1/#comment-14213</guid>
		<description>Well the popular the software become more hacks you will see. I am happy i opt for wordpress. Was hacked just once that too because i didn&#039;t updated it for more than an year. 

We should look at Drupal. Everyweek there is some new vulnerablity patch.</description>
		<content:encoded><![CDATA[<p>Well the popular the software become more hacks you will see. I am happy i opt for wordpress. Was hacked just once that too because i didn&#8217;t updated it for more than an year. </p>
<p>We should look at Drupal. Everyweek there is some new vulnerablity patch.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael VanDeMar</title>
		<link>http://smackdown.blogsblogsblogs.com/2008/03/23/new-wordpress-233-exploitvulnerability-adds-spam-directory-wp-content1/comment-page-2/#comment-13817</link>
		<dc:creator>Michael VanDeMar</dc:creator>
		<pubDate>Tue, 17 Mar 2009 23:02:06 +0000</pubDate>
		<guid isPermaLink="false">http://smackdown.blogsblogsblogs.com/2008/03/23/new-wordpress-233-exploitvulnerability-adds-spam-directory-wp-content1/#comment-13817</guid>
		<description>Actually WrathChylde, I am not sure what you are talking about. changing passwords would not cause the files to be deleted.</description>
		<content:encoded><![CDATA[<p>Actually WrathChylde, I am not sure what you are talking about. changing passwords would not cause the files to be deleted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WrathChylde</title>
		<link>http://smackdown.blogsblogsblogs.com/2008/03/23/new-wordpress-233-exploitvulnerability-adds-spam-directory-wp-content1/comment-page-2/#comment-13816</link>
		<dc:creator>WrathChylde</dc:creator>
		<pubDate>Tue, 17 Mar 2009 22:04:50 +0000</pubDate>
		<guid isPermaLink="false">http://smackdown.blogsblogsblogs.com/2008/03/23/new-wordpress-233-exploitvulnerability-adds-spam-directory-wp-content1/#comment-13816</guid>
		<description>Had the exact same problem on a 2.7.1 install. Turns out, it was a trojan virus on one of the laptops accessing wordpress.

We changed the root, and user passwords, the files went away.</description>
		<content:encoded><![CDATA[<p>Had the exact same problem on a 2.7.1 install. Turns out, it was a trojan virus on one of the laptops accessing wordpress.</p>
<p>We changed the root, and user passwords, the files went away.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tiherp</title>
		<link>http://smackdown.blogsblogsblogs.com/2008/03/23/new-wordpress-233-exploitvulnerability-adds-spam-directory-wp-content1/comment-page-2/#comment-10850</link>
		<dc:creator>tiherp</dc:creator>
		<pubDate>Fri, 30 Jan 2009 07:51:37 +0000</pubDate>
		<guid isPermaLink="false">http://smackdown.blogsblogsblogs.com/2008/03/23/new-wordpress-233-exploitvulnerability-adds-spam-directory-wp-content1/#comment-10850</guid>
		<description>May be due to the theme we used.......don&#039;t know why actually.......but the same thing happened to me too.....but managed at last.......may be this is due to the version.</description>
		<content:encoded><![CDATA[<p>May be due to the theme we used&#8230;&#8230;.don&#8217;t know why actually&#8230;&#8230;.but the same thing happened to me too&#8230;..but managed at last&#8230;&#8230;.may be this is due to the version.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lenen</title>
		<link>http://smackdown.blogsblogsblogs.com/2008/03/23/new-wordpress-233-exploitvulnerability-adds-spam-directory-wp-content1/comment-page-2/#comment-10507</link>
		<dc:creator>lenen</dc:creator>
		<pubDate>Sun, 26 Oct 2008 22:27:33 +0000</pubDate>
		<guid isPermaLink="false">http://smackdown.blogsblogsblogs.com/2008/03/23/new-wordpress-233-exploitvulnerability-adds-spam-directory-wp-content1/#comment-10507</guid>
		<description>How can Wordpress be so vulnerable? I don&#039;t get it.</description>
		<content:encoded><![CDATA[<p>How can Wordpress be so vulnerable? I don&#8217;t get it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael VanDeMar</title>
		<link>http://smackdown.blogsblogsblogs.com/2008/03/23/new-wordpress-233-exploitvulnerability-adds-spam-directory-wp-content1/comment-page-2/#comment-10492</link>
		<dc:creator>Michael VanDeMar</dc:creator>
		<pubDate>Wed, 22 Oct 2008 16:08:38 +0000</pubDate>
		<guid isPermaLink="false">http://smackdown.blogsblogsblogs.com/2008/03/23/new-wordpress-233-exploitvulnerability-adds-spam-directory-wp-content1/#comment-10492</guid>
		<description>fedmich, you can also simply turn indexing off altogether in that directory (or all of them) using .htaccess like so:

Options -Indexes

That&#039;s recursive, so it will apply to any directory under the directory you put it in, unless that directory overrides it using it&#039;s own .htaccess file.

Note, though, that (and the one you suggested) just pertain to directory browsing. If a plugin has a specific file that could be looked for directly, it could still be detected.

As to getting hacked on 2.5.1, yeah, I did as well. 2.5.2 was a security upgrade iirc. I just didn&#039;t blog about that one. It wasn&#039;t as widespread and I didn&#039;t have time when it happened.</description>
		<content:encoded><![CDATA[<p>fedmich, you can also simply turn indexing off altogether in that directory (or all of them) using .htaccess like so:</p>
<p>Options -Indexes</p>
<p>That&#8217;s recursive, so it will apply to any directory under the directory you put it in, unless that directory overrides it using it&#8217;s own .htaccess file.</p>
<p>Note, though, that (and the one you suggested) just pertain to directory browsing. If a plugin has a specific file that could be looked for directly, it could still be detected.</p>
<p>As to getting hacked on 2.5.1, yeah, I did as well. 2.5.2 was a security upgrade iirc. I just didn&#8217;t blog about that one. It wasn&#8217;t as widespread and I didn&#8217;t have time when it happened.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fedmich</title>
		<link>http://smackdown.blogsblogsblogs.com/2008/03/23/new-wordpress-233-exploitvulnerability-adds-spam-directory-wp-content1/comment-page-2/#comment-10489</link>
		<dc:creator>fedmich</dc:creator>
		<pubDate>Wed, 22 Oct 2008 15:43:48 +0000</pubDate>
		<guid isPermaLink="false">http://smackdown.blogsblogsblogs.com/2008/03/23/new-wordpress-233-exploitvulnerability-adds-spam-directory-wp-content1/#comment-10489</guid>
		<description>1 of my website got attacked too. and its wp 2.5.1

anyway, guys make sure your wp-content has a file .htaccess
and contains
IndexIgnore */*
so hackers wont be able to browse on your /wp-content/plugins/ and then check if your site can be hacked using some of your plugins.

Thanks for the post Michael :)</description>
		<content:encoded><![CDATA[<p>1 of my website got attacked too. and its wp 2.5.1</p>
<p>anyway, guys make sure your wp-content has a file .htaccess<br />
and contains<br />
IndexIgnore */*<br />
so hackers wont be able to browse on your /wp-content/plugins/ and then check if your site can be hacked using some of your plugins.</p>
<p>Thanks for the post Michael <img src='http://smackdown.blogsblogsblogs.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eugen J</title>
		<link>http://smackdown.blogsblogsblogs.com/2008/03/23/new-wordpress-233-exploitvulnerability-adds-spam-directory-wp-content1/comment-page-2/#comment-6669</link>
		<dc:creator>Eugen J</dc:creator>
		<pubDate>Thu, 03 Jul 2008 15:48:38 +0000</pubDate>
		<guid isPermaLink="false">http://smackdown.blogsblogsblogs.com/2008/03/23/new-wordpress-233-exploitvulnerability-adds-spam-directory-wp-content1/#comment-6669</guid>
		<description>If you got attacked, check http://www.bloggerguide.net/blog-platform/wordpress/wordpress-exploit-giving-backlinks-redirects-and-headaches-but-no-visitors/ too. Still working to see where the problem comes from and what tha attacker finds vulnerable.</description>
		<content:encoded><![CDATA[<p>If you got attacked, check <a href="http://www.bloggerguide.net/blog-platform/wordpress/wordpress-exploit-giving-backlinks-redirects-and-headaches-but-no-visitors/" rel="nofollow">http://www.bloggerguide.net/bl.....-visitors/</a> too. Still working to see where the problem comes from and what tha attacker finds vulnerable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WordPress Vulnerability</title>
		<link>http://smackdown.blogsblogsblogs.com/2008/03/23/new-wordpress-233-exploitvulnerability-adds-spam-directory-wp-content1/comment-page-2/#comment-6421</link>
		<dc:creator>WordPress Vulnerability</dc:creator>
		<pubDate>Thu, 26 Jun 2008 10:22:08 +0000</pubDate>
		<guid isPermaLink="false">http://smackdown.blogsblogsblogs.com/2008/03/23/new-wordpress-233-exploitvulnerability-adds-spam-directory-wp-content1/#comment-6421</guid>
		<description>[...] you see is a list of sites that were hacked through the latest WordPress Vulnerability that allows hackers to insert spam into your [...]</description>
		<content:encoded><![CDATA[<p>[...] you see is a list of sites that were hacked through the latest WordPress Vulnerability that allows hackers to insert spam into your [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
