An update for the popular blogging software WordPress was just released. The developers classify the update as a security update, it appears however that it fixes no zero day vulnerability.
The WordPress blog lists the following security enhancements and fixes in WordPress 3.1.3.
- Various security hardening
- Taxonomy query hardening
- Prevent sniffing out user names of non-authors by using canonical redirects.
- Media security fixes
- Improves file upload security on hosts with dangerous security settings.
- Cleans up old WordPress import files if the import does not finish.
- Introduce “clickjacking” protection in modern browsers on admin and login pages.
Interested users can consult WordPress trac for detailed information on all fixes that have been applied to this release.
The developers have added quite some security hardening to the new release as you can see from the list of changes above. It is still recommended to update WordPress installations as soon as possible to improve security and close the security and privacy vulnerabilities fixed in the release.
Self-hosted WordPress blogs are already picking up on the update and notifying administrators in the dashboard about the update.

It is as usual possible to apply and install the WordPress update right from the admin dashboard, or by downloading the new release from WordPress to install it manually by uploading file to the server.
The WordPress Codex lists the file changes in this new release.
Related Articles:
WordPress 3.1.4 Security Update ReleasedWordPress 2.8.5 Security Update
WordPress 3.02 Security Update Released
WordPress 2.6.5 Security Update
WordPress 3.1.2 Released, Security Update
Enjoyed the article?: Then sign-up for our free newsletter or RSS feed to kick off your day with the latest technology news and tips, or share the article with your friends and contacts on Facebook, Twitter or Google+ using the icons below.

Beat me to it. I woke up this morning and posted about this on my blog, and your date is earlier than mine, hehe. :)
Does this apply to the WISP environment too?