Comments on: Recommended Update: WordPress 2.0.6 http://www.blogherald.com/2007/01/07/recommended-update-wordpress-206/ The leading source of news covering social media and the blogosphere. Sun, 12 Feb 2012 13:36:18 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Fundraiser http://www.blogherald.com/2007/01/07/recommended-update-wordpress-206/comment-page-1/#comment-148927 Fundraiser Thu, 18 Jan 2007 21:10:34 +0000 http://www.blogherald.com/2007/01/07/recommended-update-wordpress-206/#comment-148927 A few questions from a blog idiot How do you keep the spammers from eating you alive? i\'ve seen blogs with nothing but spam postings. How do you keep some left wing extremist from posting racist or defamatory rhetoric? and if you cant stop them, what are you legally liabel when they do? can viruses be posted to blogs? A few questions from a blog idiot

How do you keep the spammers from eating you alive? i\’ve seen blogs with nothing but spam postings.

How do you keep some left wing extremist from posting racist or defamatory rhetoric? and if you cant stop them, what are you legally liabel when they do?

can viruses be posted to blogs?

]]> By: Mark http://www.blogherald.com/2007/01/07/recommended-update-wordpress-206/comment-page-1/#comment-143855 Mark Sun, 07 Jan 2007 23:21:05 +0000 http://www.blogherald.com/2007/01/07/recommended-update-wordpress-206/#comment-143855 This security issue has been found in specifically on Wordpress 2.0.5's template.php allows a user with access to the templates.php to insert arbitrary HTML and/or Javascript which can be then executed by other administrators. The link title of recent accessed files is not sanitized which causes the HTML tags ending with "/" fail. Prior to 2.0.6 release, the temporary workaround is using open "IMG" tags which only works on Firefox and Internet Explorer This security issue has been found in specifically on WordPress 2.0.5′s template.php allows a user with access to the templates.php to insert arbitrary HTML and/or Javascript which can be then executed by other administrators. The link title of recent accessed files is not sanitized which causes the HTML tags ending with “/” fail. Prior to 2.0.6 release, the temporary workaround is using open “IMG” tags which only works on Firefox and Internet Explorer

]]>