The WordPress team released a new version of WordPress to address security and maintenance issues. WordPress 4.7.1 addresses 62 bugs and 8 security issues. Because of the security fixes, it’s recommended that you update immediately to avoid someone exploiting the vulnerabilities. WordPress 4.7 was released back in December, so it’s nice to see an update within a month that addresses both security issues and bugs. In case you still need a reason to update your installation, here are the security issues fixed with this release:
- Remote code execution (RCE) in PHPMailer – No specific issue appears to affect WordPress or any of the major plugins we investigated but, out of an abundance of caution, we updated PHPMailer in this release. This issue was reported to PHPMailer by Dawid Golunski and Paul Buonopane.
- The REST API exposed user data for all users who had authored a post of a public post type. WordPress 4.7.1 limits this to only post types which have specified that they should be shown within the REST API. Reported by Krogsgard and Chris Jean.
- Cross-site scripting (XSS) via the plugin name or version header on
update-core.php. Reported by Dominik Schilling of the WordPress Security Team.
- Cross-site request forgery (CSRF) bypass via uploading a Flash file. Reported by Abdullah Hussam.
- Cross-site scripting (XSS) via theme name fallback. Reported by Mehmet Ince.
- Post via email checks
mail.example.comif default settings aren’t changed. Reported by John Blackbourn of the WordPress Security Team.
- A cross-site request forgery (CSRF) was discovered in the accessibility mode of widget editing. Reported by Ronnie Skansing.
- Weak cryptographic security for multisite activation key. Reported by Jack.
And lastly, if your site is powered by WordPress, I highly recommend taking a look at our best WordPress hosting providers to see how your hosting provider stacks up. And if you’re looking for hosting, take a look at the list to find the right host for you.