<?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>Коментарі для запису: XSS уразливість на wordpress.com</title>
	<link>http://websecurity.com.ua/2030/</link>
	<description></description>
	<pubDate>Sun, 12 Apr 2026 22:00:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=MustLive Edition</generator>

	<item>
		<title>від: MustLive</title>
		<link>http://websecurity.com.ua/2030/#comment-122453</link>
		<pubDate>Wed, 23 Apr 2008 21:16:23 +0000</pubDate>
		<guid>http://websecurity.com.ua/2030/#comment-122453</guid>
					<description>&lt;strong&gt;beni&lt;/strong&gt;

Yes, it was fixed already, as I wrote above in my post :-) (in Ukrainian).

But the most interesting, as I wrote, that you found this hole last year, but last month there were found two XSS holes in WP (at wordpress.com), one of them was the same as yours. So WordPress developers finally fixed that hole only in 2.3.3 version.</description>
		<content:encoded><![CDATA[<p><strong>beni</strong></p>
<p>Yes, it was fixed already, as I wrote above in my post <img src='http://websecurity.com.ua/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  (in Ukrainian).</p>
<p>But the most interesting, as I wrote, that you found this hole last year, but last month there were found two XSS holes in WP (at wordpress.com), one of them was the same as yours. So WordPress developers finally fixed that hole only in 2.3.3 version.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>від: beni</title>
		<link>http://websecurity.com.ua/2030/#comment-122452</link>
		<pubDate>Wed, 23 Apr 2008 21:06:19 +0000</pubDate>
		<guid>http://websecurity.com.ua/2030/#comment-122452</guid>
					<description>Hasn't this XSS vuln been fixed yet %-) ?

- beni</description>
		<content:encoded><![CDATA[<p>Hasn&#8217;t this XSS vuln been fixed yet %-) ?</p>
<p>- beni
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
