WordPress announced the release of their latest version 2.1.3 yesterday. There is a nasty SQL injection problem with that version and there is exploit code floating around out there. I have seen the code and I would recommend upgrading as soon as possible if you are in fact running version 2.1.2. Otherwise you could start having postings appear that you never wrote.
These releases include fixes for several publicly known minor XSS issues, one major XML-RPC issue, and a proactive full sweep of the WordPress codebase to protect against future problems.
We have upgraded. Unlike my lazy speed-to-patch times last go round.
From Secunia:
Description:
Sumit Siddharth has discovered two vulnerabilities in WordPress, which can be exploited by malicious users to conduct SQL injection attacks or to bypass certain security restrictions.1) Input passed to the “mt.setPostCategories” method in xmlrpc.php is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
Successful exploitation allows e.g. retrieving usernames and password hashes, but requires valid user credentials.
2) A vulnerability is caused due to improper authentication verification in xmlrpc.php. A user with contributor permissions can exploit this issue to publish posts.
Successful exploitation requires valid user credentials.
The vulnerabilities are confirmed in version 2.1.2. Other versions may also be affected.
[tags]Wordpress 2.1.2, Blog, Vulnerability[/tags]