Modernizing Authentication — What It Takes to Transform Secure Access
The WordPress 3.1.4 release follows the 3.1.3 update that came out at the end of May.
"This release fixes an issue that could allow a malicious editor-level user to gain further access to the site," WordPress developer Ryan Boren blogged.
Boren noted that WordPress 3.1.4 also incorporates several other security fixes and hardening measures. One such update is identified in changeset 18356, which provides new hardening and sanitizers for WPLANG and new admin email setup.https://o1.qnsr.com/log/p.gif?;n=203;c=204650394;s=9477;x=7936;f=201801171506010;u=j;z=TIMESTAMP;a=20392931;e=iThere are also new santization elementS for the order of get_bookmarks(),get_pages() and get_terms(). Code sanitization is intended to help ensure that bad input can't make it into the system that could potentially be leveraged by an attacker to exploit the system.
Another big shift with WordPress 3.2 comes in the form of the minimum requirements. The Microsoft IE6 browser will no longer be supported and the server requirements have also changed and no longer support PHP 4.
"As a reminder, we've bumped our minimum requirements for version 3.2 to PHP 5.2.4 and MySQL 5.0," Boren said.
Sean Michael Kerner is a senior editor at , the network for technology professionals.