WordPress 3.0.2 was released yesterday and it is highly reccomended that you do the update. The recent update for WordPress addresses some bugs and a securty flaw in all older versions of the program.Below is the summary of what this release addresses.
WordPress 3.0.2 is available and is a mandatory security update for all previous WordPress versions. Haiku has become traditional:
Fixed on day zero
One-click update makes you safe
This used to be hard
This maintenance release fixes a moderate security issue that could allow a malicious Author-level user to gain further access to the site, addresses a handful of bugs, and provides some additional security enhancements. Big thanks to Vladimir Kolesnikov for detailed and responsible disclosure of the security issue!
Download 3.0.2 or update automatically from the Dashboard > Updates menu in your site’s admin area. You should update immediately even if you do not have untrusted users.
- Fix moderate security issue where a malicious Author-level user could gain further access to the site. (r16625)
Other bugs and security hardening:
- Remove pingback/trackback blogroll whitelisting feature as it can easily be abused. (#13887)
- Fix canonical redirection for permalinks containing %category% with nested categories and paging. (#13471)
- Fix occasional irrelevant error messages on plugin activation. (#15062)
- Minor XSS fixes in request_filesystem_credentials() and when deleting a plugin. (r16367, r16373)
- Clarify the license in the readme (r15534)
- Multisite: Fix the delete_user meta capability (r15562)
- Multisite: Force current_user_can_for_blog() to run map_meta_cap() even for super admins (#15122)
- Multisite: Fix ms-files.php content type headers when requesting a URL with a query string (#14450)
- Multisite: Fix the usage of the SUBDOMAIN_INSTALL constant for upgraded WordPress MU installs (#14536)