Software Update: WordPress 5.0.1

Version 5.0.1 of WordPress has been released. With this program, which is made available under a GPL, it is possible to set up and maintain a website or blog. WordPress is easy to set up and can be up and running within five minutes if a server with PHP and MySQL is already available. There are possibilities to further extend the functionality of WordPress with plugins and the look with themes to adjust.

Version 5.0 includes a completely redesigned editor and a new default theme. The old editor is also still present and is now called classic editor. The release notes for this release can be found below. Several security vulnerabilities have been fixed in this update.

WordPress 5.0.1 Security Release

WordPress 5.0.1 is now available. This is a security release for all versions since WordPress 3.7. We strongly encourage you to update your sites immediately.

Plugin authors are encouraged to read the 5.0.1 developer notes for information on backwards compatibility.

WordPress versions 5.0 and earlier are affected by the following bugs, which are fixed in version 5.0.1. Updated versions of WordPress 4.9 and older releases are also available, for users who have not yet updated to 5.0.

• Karim El Ouerghemmic discovered that authors could alter meta data to delete files that they weren’t authorized to.
• Simon Scannell of RIPS Technologies discovered that authors could create posts of unauthorized post types with specially crafted input.
• Sam Thomas discovered that contributors could craft meta data in a way that resulted in PHP object injection.
• Tim Coen discovered that contributors could edit new comments from higher-privileged users, potentially leading to a cross-site scripting vulnerability.
• Tim Coen also discovered that specially crafted URL inputs could lead to a cross-site scripting vulnerability in some circumstances. WordPress itself was not affected, but plugins could be in some situations.
• Team Yoast discovered that the user activation screen could be indexed by search engines in some uncommon configurations, leading to exposure of email addresses, and in some rare cases, default generated passwords.
• Tim Coen and Slavco discovered that authors on Apache-hosted sites could upload specifically crafted files that bypass MIME verification, leading to a cross-site scripting vulnerability.