<?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"
	>
<channel>
	<title>Comments on: XSS vulnerabilities fixed in Wordpress 2.0.3</title>
	<atom:link href="http://www.lightbluetouchpaper.org/2006/06/02/xss-vulnerabilities-fixed-in-wordpress-203/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lightbluetouchpaper.org/2006/06/02/xss-vulnerabilities-fixed-in-wordpress-203/</link>
	<description>Security Research, Computer Laboratory, University of Cambridge</description>
	<pubDate>Sun, 06 Jul 2008 12:11:51 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Light Blue Touchpaper &#187; Oracle attack on Wordpress</title>
		<link>http://www.lightbluetouchpaper.org/2006/06/02/xss-vulnerabilities-fixed-in-wordpress-203/#comment-598</link>
		<dc:creator>Light Blue Touchpaper &#187; Oracle attack on Wordpress</dc:creator>
		<pubDate>Thu, 22 Jun 2006 13:07:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/06/02/xss-vulnerabilities-fixed-in-wordpress-203/#comment-598</guid>
		<description>[...] This post describes the second of two vulnerabilities I found in Wordpress. The first, a XSS vulnerability, was described last week. While the vulnerability discussed here is applicable in fewer cases than the previous one, it is an example of a comparatively rare class, oracle attacks, so I think merits further exposition. [...]</description>
		<content:encoded><![CDATA[<p>[...] This post describes the second of two vulnerabilities I found in Wordpress. The first, a XSS vulnerability, was described last week. While the vulnerability discussed here is applicable in fewer cases than the previous one, it is an example of a comparatively rare class, oracle attacks, so I think merits further exposition. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Light Blue Touchpaper &#187; Anatomy of an XSS exploit</title>
		<link>http://www.lightbluetouchpaper.org/2006/06/02/xss-vulnerabilities-fixed-in-wordpress-203/#comment-574</link>
		<dc:creator>Light Blue Touchpaper &#187; Anatomy of an XSS exploit</dc:creator>
		<pubDate>Tue, 13 Jun 2006 08:27:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/06/02/xss-vulnerabilities-fixed-in-wordpress-203/#comment-574</guid>
		<description>[...] Last week I promised to follow up on a few XSS bugs that I found in Wordpress. The vulnerabilities are fixed in Wordpress 2.0.3, even though the release notes do not mention their existence. I think there are a number of useful lessons that can be drawn from them, so in this post I will describe some more details. [...]</description>
		<content:encoded><![CDATA[<p>[...] Last week I promised to follow up on a few XSS bugs that I found in Wordpress. The vulnerabilities are fixed in Wordpress 2.0.3, even though the release notes do not mention their existence. I think there are a number of useful lessons that can be drawn from them, so in this post I will describe some more details. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ha.ckers.org security lab - Archive &#187; XSS, Redirects and SEO</title>
		<link>http://www.lightbluetouchpaper.org/2006/06/02/xss-vulnerabilities-fixed-in-wordpress-203/#comment-572</link>
		<dc:creator>ha.ckers.org security lab - Archive &#187; XSS, Redirects and SEO</dc:creator>
		<pubDate>Mon, 12 Jun 2006 22:48:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2006/06/02/xss-vulnerabilities-fixed-in-wordpress-203/#comment-572</guid>
		<description>[...] As a side note, I was talking with quadzilla from SEO Blackhat (who, btw, is running a SEO blackjact tournament for anyone who is interested) and he gave me another idea regarding XSS detection that I have been thinking about for quite a while. One of the major problems on the internet today is the fact that a ton of websites are running canned software with bugs in it (drupal, PHP-Nuke, Wordpress ,etc&#8230;). If you subscribe to some of the webappsec mailing lists you probably can see the sheer volume of new XSS exploits being discovered on a daily basis. It&#8217;s fairly trivial to use Google to detect which websites are running the software in particular (by searching by keywords used by that software), and then use the returned lists of sites to launch automated XSS attacks, to improve pagerank. Pretty scary, and pretty easy. [...]</description>
		<content:encoded><![CDATA[<p>[...] As a side note, I was talking with quadzilla from SEO Blackhat (who, btw, is running a SEO blackjact tournament for anyone who is interested) and he gave me another idea regarding XSS detection that I have been thinking about for quite a while. One of the major problems on the internet today is the fact that a ton of websites are running canned software with bugs in it (drupal, PHP-Nuke, Wordpress ,etc&#8230;). If you subscribe to some of the webappsec mailing lists you probably can see the sheer volume of new XSS exploits being discovered on a daily basis. It&#8217;s fairly trivial to use Google to detect which websites are running the software in particular (by searching by keywords used by that software), and then use the returned lists of sites to launch automated XSS attacks, to improve pagerank. Pretty scary, and pretty easy. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
