<?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: Dangerous WordPress Exploit Made Public</title>
	<atom:link href="http://blogsecurity.net/wordpress/dangerous-wordpress-exploit-made-public/feed" rel="self" type="application/rss+xml" />
	<link>http://blogsecurity.net/wordpress/dangerous-wordpress-exploit-made-public</link>
	<description>Always something worth reading...</description>
	<lastBuildDate>Fri, 12 Mar 2010 11:09:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Wordpress 2.3 &#8230; ponte una beta YA! &#171; beGNU</title>
		<link>http://blogsecurity.net/wordpress/dangerous-wordpress-exploit-made-public/comment-page-1#comment-1236</link>
		<dc:creator>Wordpress 2.3 &#8230; ponte una beta YA! &#171; beGNU</dc:creator>
		<pubDate>Sat, 22 Sep 2007 17:22:49 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/dangerous-wordpress-exploit-made-public/#comment-1236</guid>
		<description>[...] Wordpress 2.3 en español Exploit liberado Noticia original sobre el exploit [...]</description>
		<content:encoded><![CDATA[<p>[...] Wordpress 2.3 en español Exploit liberado Noticia original sobre el exploit [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blux 2.0 &#187; Blog Archive &#187; Peligroso Exploit para WordPress liberado</title>
		<link>http://blogsecurity.net/wordpress/dangerous-wordpress-exploit-made-public/comment-page-1#comment-1127</link>
		<dc:creator>Blux 2.0 &#187; Blog Archive &#187; Peligroso Exploit para WordPress liberado</dc:creator>
		<pubDate>Mon, 17 Sep 2007 03:24:27 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/dangerous-wordpress-exploit-made-public/#comment-1127</guid>
		<description>[...] solución a éste problema BlogSecurity sugiere a los blogger que tenemos montado nuestro blog en éste popular CM, que actualicemos a la [...]</description>
		<content:encoded><![CDATA[<p>[...] solución a éste problema BlogSecurity sugiere a los blogger que tenemos montado nuestro blog en éste popular CM, que actualicemos a la [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Berita IT &#187; Blog Archive &#187; Exploit Wordpress Dirilis</title>
		<link>http://blogsecurity.net/wordpress/dangerous-wordpress-exploit-made-public/comment-page-1#comment-1059</link>
		<dc:creator>Berita IT &#187; Blog Archive &#187; Exploit Wordpress Dirilis</dc:creator>
		<pubDate>Fri, 14 Sep 2007 14:13:34 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/dangerous-wordpress-exploit-made-public/#comment-1059</guid>
		<description>[...] Sumber: BlogSecurity [...]</description>
		<content:encoded><![CDATA[<p>[...] Sumber: BlogSecurity [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Publicado exploit peligroso para Wordpress 2.2.2 &#124; La WeB de DragoN</title>
		<link>http://blogsecurity.net/wordpress/dangerous-wordpress-exploit-made-public/comment-page-1#comment-1030</link>
		<dc:creator>Publicado exploit peligroso para Wordpress 2.2.2 &#124; La WeB de DragoN</dc:creator>
		<pubDate>Thu, 13 Sep 2007 18:59:25 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/dangerous-wordpress-exploit-made-public/#comment-1030</guid>
		<description>[...] BlogSecurity me entero que en Milw0rm se ha publicado un exploit que permite atacar múltiples vulnerabilidades [...]</description>
		<content:encoded><![CDATA[<p>[...] BlogSecurity me entero que en Milw0rm se ha publicado un exploit que permite atacar múltiples vulnerabilidades [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gefährlicher Wordpress-Exploit veröffentlicht &#124; wordpress &#124; XSBlog2.0beta</title>
		<link>http://blogsecurity.net/wordpress/dangerous-wordpress-exploit-made-public/comment-page-1#comment-1029</link>
		<dc:creator>Gefährlicher Wordpress-Exploit veröffentlicht &#124; wordpress &#124; XSBlog2.0beta</dc:creator>
		<pubDate>Thu, 13 Sep 2007 15:54:25 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/dangerous-wordpress-exploit-made-public/#comment-1029</guid>
		<description>[...] BlogSecurity Tags: aktuelles , Exploit , Security , wordpress Popularity: unranked [...]</description>
		<content:encoded><![CDATA[<p>[...] BlogSecurity Tags: aktuelles , Exploit , Security , wordpress Popularity: unranked [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Boozox &#187; Urgente, actualizar Wordpress a 2.2.3</title>
		<link>http://blogsecurity.net/wordpress/dangerous-wordpress-exploit-made-public/comment-page-1#comment-1027</link>
		<dc:creator>Boozox &#187; Urgente, actualizar Wordpress a 2.2.3</dc:creator>
		<pubDate>Thu, 13 Sep 2007 15:20:57 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/dangerous-wordpress-exploit-made-public/#comment-1027</guid>
		<description>[...] la noticia original apuntan que cerca del 50% de los blogs administrados con Wordpress están en riesgo por este [...]</description>
		<content:encoded><![CDATA[<p>[...] la noticia original apuntan que cerca del 50% de los blogs administrados con Wordpress están en riesgo por este [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SigT</title>
		<link>http://blogsecurity.net/wordpress/dangerous-wordpress-exploit-made-public/comment-page-1#comment-1023</link>
		<dc:creator>SigT</dc:creator>
		<pubDate>Thu, 13 Sep 2007 10:42:42 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/dangerous-wordpress-exploit-made-public/#comment-1023</guid>
		<description>&lt;strong&gt;Exploit peligroso para WordPress es liberado...&lt;/strong&gt;

En BlogSecurity comentan que en un archivo de exploits llamado Milw0rm se ha publicado un exploit que dice poder atacar múltiples versiones de WordPress: 2.2, 2.2.2, 2.0.5, 2.0.6, 2.1, etcétera.

Las pruebas del exploit se han hecho con PHP 5.2.4, Ap...</description>
		<content:encoded><![CDATA[<p><strong>Exploit peligroso para WordPress es liberado&#8230;</strong></p>
<p>En BlogSecurity comentan que en un archivo de exploits llamado Milw0rm se ha publicado un exploit que dice poder atacar múltiples versiones de WordPress: 2.2, 2.2.2, 2.0.5, 2.0.6, 2.1, etcétera.</p>
<p>Las pruebas del exploit se han hecho con PHP 5.2.4, Ap&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iKA&#8217;s Blog &#187; WP-Exploid öffentlich</title>
		<link>http://blogsecurity.net/wordpress/dangerous-wordpress-exploit-made-public/comment-page-1#comment-1021</link>
		<dc:creator>iKA&#8217;s Blog &#187; WP-Exploid öffentlich</dc:creator>
		<pubDate>Thu, 13 Sep 2007 10:23:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/dangerous-wordpress-exploit-made-public/#comment-1021</guid>
		<description>[...] brachte heute Morgen die Meldung, dass ein Exploid f&#252;r WordPress &#246;ffentlich wurde. Da das Toolkit somit leicht [...]</description>
		<content:encoded><![CDATA[<p>[...] brachte heute Morgen die Meldung, dass ein Exploid f&#252;r WordPress &#246;ffentlich wurde. Da das Toolkit somit leicht [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Kierznowski</title>
		<link>http://blogsecurity.net/wordpress/dangerous-wordpress-exploit-made-public/comment-page-1#comment-1019</link>
		<dc:creator>David Kierznowski</dc:creator>
		<pubDate>Thu, 13 Sep 2007 10:06:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/dangerous-wordpress-exploit-made-public/#comment-1019</guid>
		<description>Daniel, Phil: This is why defense in depth is so important. As Daniel mentioned, upgrading is a simple step, but there are so many other layers that we need in top of this. 
&lt;br /&gt;
Hopefully the Mod_Sec guide and Phil&#039;s whitepaper will help build up some of these layers.
&lt;br /&gt;
As for WordPress themselves, a full blown, carefully layed out SDL is required me thinks.</description>
		<content:encoded><![CDATA[<p>Daniel, Phil: This is why defense in depth is so important. As Daniel mentioned, upgrading is a simple step, but there are so many other layers that we need in top of this.<br />
<br />
Hopefully the Mod_Sec guide and Phil&#8217;s whitepaper will help build up some of these layers.<br />
<br />
As for WordPress themselves, a full blown, carefully layed out SDL is required me thinks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philipp</title>
		<link>http://blogsecurity.net/wordpress/dangerous-wordpress-exploit-made-public/comment-page-1#comment-1018</link>
		<dc:creator>Philipp</dc:creator>
		<pubDate>Thu, 13 Sep 2007 09:33:51 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/wordpress/dangerous-wordpress-exploit-made-public/#comment-1018</guid>
		<description>Really interesting that a security team isn&#039;t even using a version near the latest stable(secure) Wordpress version. But I can ensure that BlogSec runs with the latest one :), although that may mean nothing about security itself...</description>
		<content:encoded><![CDATA[<p>Really interesting that a security team isn&#8217;t even using a version near the latest stable(secure) Wordpress version. But I can ensure that BlogSec runs with the latest one :), although that may mean nothing about security itself&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
