
In this article
When a security flaw is found in a plugin, theme or platform, the fix is published along with a description of the flaw. Attackers read those notes too, and bots scan the internet for sites that have not updated yet. Keeping software current is the single most effective way to stay out of that net.
This applies to any platform, whether your site runs on WordPress, Joomla, Drupal, Magento, a hosted builder or custom code with third-party libraries. Hosted builders such as Shopify, Wix and Squarespace update their core for you, but apps, embeds and your own theme code can still go stale.
Why old software gets hacked
- Flaws are public. Once a fix is released, anyone can learn what was wrong and try it on sites that have not updated.
- Attacks are automatic. Bots test thousands of sites an hour, so small or unknown sites are not safe by being obscure.
- Abandoned code gets no fixes. A plugin or theme that is no longer maintained keeps its flaws forever.
Step 1: list everything your site runs
Write down the platform and its version, the theme, every plugin or extension, any third-party scripts and libraries, and your server software such as PHP, Node or the database. You cannot update what you do not know you have. Run a free outside scan to see what your public pages load and whether anything looks tampered with.
Step 2: find what is out of date
- Check the update screen of your platform's admin area for core, theme and plugin updates.
- Look at when each plugin was last updated. If it has had no update in over a year, or the author has stopped supporting it, plan to replace it.
- Check which PHP or runtime version your host uses. Old versions stop receiving security fixes, so ask your host about upgrading.
- Look at the version numbers of front-end libraries in your page source. Old copies of popular scripts are a common weak spot.
Step 3: update safely
- Back up first. Make a full copy of files and database, and know how to restore it.
- Test on a staging copy for important or complex sites, so a bad update does not hit visitors.
- Update one thing at a time, or in small groups, so you can tell what caused a problem.
- Update security fixes quickly. Do not wait weeks for a release that patches a known flaw.
- Check key pages afterwards: home, a form, checkout and the login page.
Step 4: remove what you do not need
Deactivated plugins and unused themes still sit on your server, and some can still be attacked. Delete them, not just switch them off. Fewer components mean fewer things to keep current.
Step 5: make updates a habit
- Turn on automatic updates for minor and security releases where your platform supports it.
- Set a recurring reminder, such as every week, to review everything else.
- Subscribe to security notices from your platform and the plugins you rely on.
- Re-scan after each update, and watch for sudden changes, because an update that was tampered with or a missed one can both leave trouble behind.
If you were already behind
If your site ran old software for a long time, assume it may already be compromised. Read how to check if your website is hacked, update everything, and change your passwords and secure your logins with two-factor authentication.
Common questions
Can an update break my site?
Sometimes, which is why you back up first and test important sites on a staging copy. The risk of a broken page is small next to the risk of a hack.
Should I turn on automatic updates?
For security and minor releases, usually yes. For large version jumps, update manually after a backup and a quick test.
Are paid plugins safer than free ones?
Not automatically. What matters is whether the plugin is actively maintained and updated promptly.
My site is small. Do I still need to update?
Yes. Attacks are automated and do not look at the size of the site.
Free tools for this problem
- Website malware scanner: Spam links, malicious scripts, cloaking, bad redirects and exposed backups.
- Security headers checker: Grade HSTS, CSP, clickjacking and referrer headers, with fixes to copy.
- Page speed checker: Lighthouse score, Core Web Vitals, server response and compression.
