WordPress behind

Why it matters

WordPress fixes holes in the newest version first. Older versions get fewer and later fixes, and after a while none at all. A site that stays behind slowly collects known holes.

How Snaglist checks it

This is part of the security check, a separate check next to the crawl, in Studio and Bureau, and only on a site you have verified. Snaglist only looks at what any visitor can see from outside. It never logs in, guesses no passwords and sends no attacks. It reads the WordPress version from the site and compares it with the newest version on wordpress.org.

Common causes

• Updates were never switched on
• Fear that a plugin or theme breaks
• Nobody looks after the site any more

How to fix it

1. Make a backup of the site and the database.
2. Update WordPress, then the plugins and the theme.
3. Check the most important pages and forms.
4. Switch on automatic minor updates.
5. Run the security check again to confirm.

How it shows in the report

In the report for your client this appears under the heading "Your WordPress is out of date". When everything is in order, the report says: "WordPress is up to date".