http://blogsecurity.net/wordpress/wordpress-26-released Always something worth reading... Fri, 12 Mar 2010 11:09:45 +0000 http://wordpress.org/?v= hourly 1 http://blogsecurity.net/wordpress/wordpress-26-released/comment-page-1#comment-12465 Abel Cheung Wed, 30 Jul 2008 09:20:23 +0000 http://blogsecurity.net/wordpress/wordpress-26-released/#comment-12465 Not only security issue, but <a href="http://blog.ryanajarrett.com/site/more-wordpress-26-problems-wordpress-turbo/" rel="nofollow">also</a> <a href="http://www.howtospoter.com/web-20/wordpress/wordpress-26-creates-problem-under-disguise-of-feature" rel="nofollow">usage</a> <a href="http://lesterchan.net/wordpress/2008/07/17/how-to-turn-off-post-revision-in-wordpress-26/" rel="nofollow">issues</a> as well. Recommending to wait till later series (sans the security patches) is definitely a yes-yes. Not only security issue, but also usage issues as well. Recommending to wait till later series (sans the security patches) is definitely a yes-yes.

]]> http://blogsecurity.net/wordpress/wordpress-26-released/comment-page-1#comment-12204 Philipp Wed, 23 Jul 2008 11:42:33 +0000 http://blogsecurity.net/wordpress/wordpress-26-released/#comment-12204 Correct, thanks for mentioning this Gareth. So everyone who, doesn't need XMLRPC, is updating to WP 2.6 should disable this feature, for security reasons. Correct, thanks for mentioning this Gareth. So everyone who, doesn’t need XMLRPC, is updating to WP 2.6 should disable this feature, for security reasons.

]]> http://blogsecurity.net/wordpress/wordpress-26-released/comment-page-1#comment-12198 Gareth Heyes Tue, 22 Jul 2008 08:17:03 +0000 http://blogsecurity.net/wordpress/wordpress-26-released/#comment-12198 XML-RPC is only off by default for new installations. Any upgrades will retain the current setting. XML-RPC is only off by default for new installations. Any upgrades will retain the current setting.

]]>