WordPress 3.1.4 is available now and is a maintenance and security update for all previous versions.<\/p>\n
This release fixes an issue that could allow a malicious Editor-level user to gain further access to the site. Thanks K. Gudinavicius of\u00a0SEC Consult<\/a>\u00a0for bringing this to our attention. Version 3.1.4 also incorporates several other security fixes and hardening measures thanks to the work of WordPress developers Alexander Concha<\/a>\u00a0and\u00a0Jon Cave<\/a> of our security team. Consult the\u00a0change log<\/a>\u00a0for more details.<\/p>\n Download WordPress 3.1.4<\/strong><\/a> or update immediately from the Dashboard \u2192 Updates menu in your site’s admin area.<\/strong><\/p>\n This release was about all that stood in the way of a final release of WordPress 3.2. So we’re also announcing the third release candidate for 3.2, which contains all of the fixes in 3.1.4; few minor RTL, JavaScript, and user interface fixes; and ensures graceful failures if 3.2 is run on PHP4. As a reminder, we’ve bumped our minimum requirements for version 3.2 to PHP 5.2.4 and MySQL 5.0.<\/p>\n To test WordPress 3.2, try the WordPress Beta Tester plugin<\/a> (you’ll want “bleeding edge nightlies”). Or you can download the release candidate here<\/a> (zip). At this stage, plugin authors should be doing final tests to ensure compatibility.<\/p>\nWordPress 3.2 Release Candidate 3<\/h3>\n