WordPress 5.0.1 Releases: Security fixes
WordPress.com is a blogging platform that is owned and hosted online by Automattic. It is run on a modified version of WordPress, an open source piece of software used by bloggers. This website provides free blog hosting for registered users and is financially supported via paid upgrades, “VIP” services and advertising.
The site opened to beta testers on August 8, 2005, and opened to the public on November 21, 2005. It was initially launched as an invitation-only service, although at one stage, accounts were also available to users of the Flock web browser. As of February 2017, over 77 million new posts and 42.7 million new comments are published monthly on the service.
The biggest highlight of WordPress 5.0 is the formal introduction of a new block-based editor, Gutenberg, to give users a more simplified editing experience. Whether you’re building a website for the first time, editing a blog, or writing code, users have more flexibility in displaying content.
The new Gutenberg editor does not change the viewer’s perception of your content. It is designed to let you quickly insert any type of multimedia and rearrange the content you want to display. Each piece of content is in its own block and has a separate package for easy operation.
In addition, WordPress 5.0 introduces a new default theme, Twenty Nineteen, which is designed for this new editor and is intended for use in a variety of use cases. Whether it’s running a photo blog, launching a new business or supporting a non-profit organization, Twenty Nineteen is flexible enough to meet your needs.
Of course, users who don’t want to change their habits can continue to use the classic editor. The Classic Editor plugin will be supported until 2021.
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 Ouerghemmi 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.