Comments on: WP 2.3.3 does not close injection spam loophole http://www.metablog.us/blogging/wp-233-does-not-close-injection-spam-loophole/ blogging about blogging about Wed, 21 Jul 2010 03:59:59 +0000 hourly 1 http://wordpress.org/?v=3.0 By: ScottS-M http://www.metablog.us/blogging/wp-233-does-not-close-injection-spam-loophole/comment-page-1/#comment-32 ScottS-M Mon, 17 Mar 2008 16:07:43 +0000 http://www.metablog.us/blogging/wp-233-does-not-close-injection-spam-loophole/#comment-32 Cookie hijacking is different than they were using before wasn't it? Funny they'd go through the trouble of getting that and then fall back to the same sort of spam as before. Cookie hijacking is different than they were using before wasn’t it? Funny they’d go through the trouble of getting that and then fall back to the same sort of spam as before.

]]> By: Aziz Poonawalla http://www.metablog.us/blogging/wp-233-does-not-close-injection-spam-loophole/comment-page-1/#comment-31 Aziz Poonawalla Mon, 17 Mar 2008 11:31:59 +0000 http://www.metablog.us/blogging/wp-233-does-not-close-injection-spam-loophole/#comment-31 I upgraded that blog the day of the 2.3.3 release, because I'd been hit before. So merely upgrading the blog doesn't remove the vulnerability? I am going ahead and changing the passwords. Thats probably best practice anyway. I upgraded that blog the day of the 2.3.3 release, because I’d been hit before. So merely upgrading the blog doesn’t remove the vulnerability?

I am going ahead and changing the passwords. Thats probably best practice anyway.

]]> By: Donncha O Caoimh http://www.metablog.us/blogging/wp-233-does-not-close-injection-spam-loophole/comment-page-1/#comment-30 Donncha O Caoimh Mon, 17 Mar 2008 09:48:58 +0000 http://www.metablog.us/blogging/wp-233-does-not-close-injection-spam-loophole/#comment-30 I think your blog was probably attacked before you upgraded and the hackers got your login cookie using some Javascript. Best thing to do is change your password! I think your blog was probably attacked before you upgraded and the hackers got your login cookie using some Javascript. Best thing to do is change your password!

]]>