WordPress 2.6.2 has been released.
Stefan Esser recently warned developers of the dangers of SQL Column Truncation and the weakness of mt_rand(). With his help we worked around these problems and are now releasing WordPress 2.6.2. If you allow open registration on your blog, you should definitely upgrade. With open registration enabled, it is possible in WordPress versions 2.6.1 and earlier to craft a username such that it will allow resetting another user’s password to a randomly generated password. The randomly generated password is not disclosed to the attacker, so this problem by itself is annoying but not a security exploit. However, this attack coupled with a weakness in the random number seeding in mt_rand() could be used to predict the randomly generated password. Stefan Esser will release details of the complete attack shortly. The attack is difficult to accomplish, but its mere possibility means we recommend upgrading to 2.6.2.
Here is a list of bugs fixed:
- Can’t control where a user redirects to when they log in
- Bug in textpattern import
- include mysql version in version check query string
- RSS widget shouldn’t link if there isn’t a link
- get_post_meta fails to unserialize when $single=false
- typing error in wp-settings.php
- comment_max_links causes confusion when zero
- get_posts not working properly
- Insert image into post always inserts full size
- Filter news on templates cant work
- Typo in post revisions
Here is a list of changed files:
2 thoughts on “WordPress 2.6.2”
I believe that I am currently running WordPress 2.6.1. Will it be a problem if I don’t update this round and wait until the next major round of updates?
2.6.2 contains a security fix, if you ask me. I would recommend you to update =D
Comments are closed.