WordPress announced on its blog a few days ago that a major security vulnerability is affecting older versions of the popular CMS platform. So please update to version 4.0.1 as a matter of urgency!
WordPress security vulnerabilities keep cropping up, and no two are alike. Following the security breach in the Revolution Slider and WP E-Commerce plugins, it is now the core of WordPress itself that is affected by a major security vulnerability!

Are you affected?
If your WordPress
installation is older than version 3.7.4
, then yes! It’s time to take a moment to update your website.
Versions 3.9.2, 3.8.4 and 3.7.4 have been automatically updated by WordPress to the new versions 3.9.3, 3.8.5 or 3.7.5.
Version 4.0 is not affected, but version 4.0.1 nevertheless fixes 23 minor bugs.
As a reminder, your WordPress version is displayed in your dashboard when you log into the admin area.
How do you update WordPress?
Before updating, it is best to back up your site to avoid any data loss. Backing up the database and the entire wp-content folder will ensure you retain a copy of your site and all its content, which you can easily reinstall.
Once the backup is complete, simply go to the dashboard and click on ‘Update’. Go to the “Update” page, where the update itself is fairly quick and shouldn’t, in theory, cause any problems. You might even want to take this opportunity to update your plugins and themes, which are sometimes prone to security vulnerabilities.
What are the risks?
According to WordPress, six major vulnerabilities
have been identified:
– Cross-site scripting
(abbreviated to XSS
) issues that a contributor or author could exploit to compromise a site. Cross-site scripting is often used to redirect users to another site for phishing purposes or to steal cookies.
See Wikipedia for cross-site scripting: http://fr.wikipedia.org/wiki/Cross-site_scripting
– Cross-Site Request Forgery
(CSRF
) attacks, which can trick users into changing their passwords.
Wikipedia on cross-site request forgery: http://fr.wikipedia.org/wiki/Cross-Site_Request_Forgery
– A bug that can lead to a denial-of-service attack when the user verifies their password.
Wikipedia on denial-of-service attacks: http://fr.wikipedia.org/wiki/Attaque_par_d%C3%A9ni_de_service
– Greater protection against Request Forgery attacks when WordPress sends an HTTPS request
– An unlikely ‘hash collision’ bug could compromise a user’s account (this required the user not to have logged in to the site since 2008…)
– And finally, the invalidation of links sent by WordPress during a password reset when the user recovers their username, password or changes their email address.



