Comments on: WordPress Plugin Related Sites 2.1 Blind SQL Injection Vulnerability http://blogsecurity.net/wordpress/wordpress-plugin-related-sites-21-blind-sql-injection-vulnerability Always something worth reading... Fri, 12 Mar 2010 11:09:45 +0000 http://wordpress.org/?v= hourly 1 By: DK http://blogsecurity.net/wordpress/wordpress-plugin-related-sites-21-blind-sql-injection-vulnerability/comment-page-1#comment-16613 DK Sat, 04 Jul 2009 19:41:42 +0000 http://blogsecurity.net/?p=555#comment-16613 Thanks for feedback chaps. Thanks for feedback chaps.

]]> By: Blog Traffic Exchange http://blogsecurity.net/wordpress/wordpress-plugin-related-sites-21-blind-sql-injection-vulnerability/comment-page-1#comment-16612 Blog Traffic Exchange Sat, 04 Jul 2009 19:29:10 +0000 http://blogsecurity.net/?p=555#comment-16612 For what it is worth I fixed this on 6/30 with 2.2.1 as soon as I realized. EVERYONE SHOULD RUN 2.2.1 nothing earlier. You should consider running BTE on this blog. For what it is worth I fixed this on 6/30 with 2.2.1 as soon as I realized.

EVERYONE SHOULD RUN 2.2.1 nothing earlier.

You should consider running BTE on this blog.

]]> By: MustLive http://blogsecurity.net/wordpress/wordpress-plugin-related-sites-21-blind-sql-injection-vulnerability/comment-page-1#comment-16603 MustLive Wed, 01 Jul 2009 17:54:14 +0000 http://blogsecurity.net/?p=555#comment-16603 <strong>David</strong> This exploit for Related Sites plugin for WordPress is not working, because there is no mentioned SQL Injection vulnerability in it. As I wrote at my site (<a href="http://websecurity.com.ua/3281/" rel="nofollow">http://websecurity.com.ua/3281/</a>). And in comments to my post I wrote in details about why this vulnerability is not working to author of this exploit. David

This exploit for Related Sites plugin for WordPress is not working, because there is no mentioned SQL Injection vulnerability in it. As I wrote at my site (http://websecurity.com.ua/3281/). And in comments to my post I wrote in details about why this vulnerability is not working to author of this exploit.

]]>