WordPress users urged to manually update to fix bug that prevents automatic updating

Posted by   Martijn Grooten on   Feb 8, 2018

WordPress has long had a bad reputation in the security community. While this is understandable – compromised installations of the popular content management system are regularly used to spread malware and spam – it is also a little unfair, as the security of WordPress has improved a lot over the years.

Indeed, exploitable vulnerabilities in the WordPress core have become quite rare, with most recent compromises using a flaw in a plug-in or theme. What has made the biggest difference to the security of its install base, though, is the ability, introduced in 2013, for WordPress installations to self-update, thus ensuring vulnerabilities are patched automatically.

Unfortunately, this feature broke in a rather bad way this week. A regular maintenance update contained a bug that triggered a fatal error when WordPress was trying to determine whether it needed updating, thus preventing any updates from being installed automatically.

The bug has since been fixed but, as you can guess, the fix won't be installed automatically. Users are thus being urged to update to WordPress 4.9.4 manually.

wordpress_logo.png

 

It is unclear whether all WordPress installations with auto-update enabled did indeed install the faulty update in the 21-hour period during which it was available, but I have seen reports of people who say their site installed both updates automatically. Though the (sparse) technical details published by WordPress don't make mention of it, is is possible that the issue only affected a subset of the install base. This could also explain how the bug passed the project's QA.

 

 

Though there are are currently no known vulnerabilities in the WordPress core, those running WordPress are strongly advised, if it hasn't auto-updated, to update to 4.9.4 manually sooner rather than later, to make sure they will be protected against future vulnerabilities. And it doesn't hurt to point out that, for the average WordPress user, the self-update function still seems a far better option than any of the available alternatives.

twitter.png
fb.png
linkedin.png
googleplus.png
reddit.png

 

Latest posts:

VB2018 paper: Uncovering the wholesale industry of social media fraud: from botnet to bulk reseller panels

Today, we publish the VB2018 paper by Masarah Paquet-Clouston (GoSecure) who looked at the supply chain behind social media fraud.

VB2018 paper: Now you see it, now you don't: wipers in the wild

Today, we publish the VB2018 paper from Saher Naumaan (BAE Systems) who looks at malware variants that contain a wiper functionality. We also publish the recording of her presentation.

Emotet trojan starts stealing full emails from infected machines

The infamous Emotet trojan has added the capability to steal full email bodies from infected machines, opening the possibilities for more targeted spam and phishing campaigns.

VB2018 paper: Who wasn’t responsible for Olympic Destroyer?

Cisco Talos researchers Paul Rascagnères and Warren Mercer were among the first to write about the Olympic Destroyer, the malware that targeted the 2018 PyeongChang Winter Olympic Games. Today, we publish the paper they presented at VB2018 about the…

VB2018 paper: From drive-by download to drive-by mining: understanding the new paradigm

Today, we publish the VB2018 paper by Malwarebytes researcher Jérôme Segura, in which he details the shift from exploit kits to drive-by mining. We also publish the video of his VB2018 presentation.

We have placed cookies on your device in order to improve the functionality of this site, as outlined in our cookies policy. However, you may delete and block all cookies from this site and your use of the site will be unaffected. By continuing to browse this site, you are agreeing to Virus Bulletin's use of data as outlined in our privacy policy.