1. WordPress 5.3.1 Security and Maintenance Release

WordPress 5.3.1 Security and Maintenance Release

WordPress 5.3.1 was released on 13 December 2019.

WordPress 5.3.1 is a security release which addresses four security issues.

As with any security release – it’s important that you update immediately.

What does it fix?

Security issues fixed in the WordPress 5.3.1:

  • a bug where an unprivileged user could make a post sticky via the REST API
  • a bug where cross-site scripting (XSS) could be stored in well-crafted links
  • a XSS vulnerability using Gutenberg block edito
  • hardening wp_kses_bad_protocol() to ensure that it is aware of the named colon attribute

There were also 48 maintenance updates covering the block editor, Twenty Twenty bundled theme, accessibility, Admin CSS, internationalization, media library and date/time handling.

How to install update?

As a minor release, by default, the update will install automatically.

If this has been disabled you will need to install by logging into your WordPress administration console and go to the Dashboard -> Updates page.

WordPress 5.2.4 Security Release

WordPress 5.2.4 was released on 14 October 2019.

WordPress 5.2.4 is a security release which addresses six security issues and two bugs.

As with any security release – it’s important that you update immediately.

What does it fix?

Security issues fixed in the WordPress 5.2.4 Security Release:

  • a bug that allowed the theme Customizer to store XSS (cross-site scripting)
  • a bug that allowed viewing unauthenticated posts
  • a bug that allowed XSS to inject JavaScript into style tags
  • a bug that provided a way to poison the cache of JSON GET requests via the Vary: Origin header
  • server-side request forgery in the way that URLs are validated
  • Props to Ben Bidner of the WordPress Security Team who discovered issues related to referrer validation in the admin

Bugs fixed:

How to install update?

As a minor release, by default, the update will install automatically.

If this has been disabled you will need to install by logging into your WordPress administration console and go to the Dashboard -> Updates page.

WordPress 5.2.3 Security Release

WordPress 5.2.3 was released on 4 September 2019.

WordPress 5.2.3 is a security release which addresses several cross-site scripting (XSS) vulnerabilities, a patch for jQuery to and includes 28 bug fixes.

As with any security release – it’s important that you update immediately.

What does it fix?

Issues fixed in the WordPress 5.2.3 Security Release:

As well as several other fixes.

How to install update?

As a minor release, by default, the update will install automatically.

If this has been disabled you will need to install by logging into your WordPress administration console and go to the Dashboard -> Updates page.

WordPress 5.0.1 Security Release

A week after WordPress 5.0 was released a new update has been announced.

WordPress 5.0.1 is a security release which resolves several vulnerabilities found in all versions since WordPress 3.7.

As with any security release – it’s important that you update immediately.

As a “minor version” update – WordPress will automatically install the update (if automatically updates haven’t been disabled). But it’s advised to check that the update has installed and your site is still functioning.

What does it fix?

Issues fixed in the WordPress 5.0.1 Security Release:

  • authors could alter meta data to delete files that they weren’t authorised to
  • authors could create posts of unauthorised post types with specially crafted input
  • contributors could craft meta data in a way that resulted in PHP object injection
  • contributors could edit new comments from higher-privileged users, potentially leading to a cross-site scripting vulnerability
  • 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.
  • 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
  • authors on Apache-hosted sites could upload specifically crafted files that bypass MIME verification, leading to a cross-site scripting vulnerability

What if you don’t want to use Gutenberg?

Many WordPress administrators had chosen to not install WordPress 5.0 to avoid the massive Gutenberg update.

With these vulnerabilities announced it’s important to update.

You could update to WordPress 5.0.1 and install the Classic Editor plugin to continue using WordPress mostly the same as before.

They’ve also released WordPress 4.9.9 – but you will need to manually update.

Either way – you really should update to patch these vulnerabilities.