Skip to content

Practical advice

Website Security Updates

The site does not announce that it is out of date. It just becomes an easy target, usually on a plugin you forgot was installed.

Back to Blog

A website feels finished the day it launches. The software underneath it does not stay finished. WordPress core, plugins, themes, the PHP version, and the server itself keep receiving fixes because people keep finding holes. Website security updates are the unglamorous habit of applying those fixes on purpose, with a backup, before someone else uses the hole. Perth small business sites get hit this way all the time. Not by a film plot. By an automated scan that tries known bugs against every site it can find.

The Australian Cyber Security Centre has said for years that unpatched software is a common way into small organisations. You do not need a private statistic to act on that. If your site runs code you have not updated since the designer handed it over, you are betting that none of the published bugs in that code apply to you. That bet gets worse every month.

What actually needs updating

Think in layers. Skipping a layer is how "we updated WordPress" still leaves you exposed.

  • The platform. On WordPress, that is core. On a hosted builder, the vendor does this and you mostly need to keep paying them and not install random extras.
  • Themes and plugins. This is the usual hole. A contact-form plugin or a slider you no longer use can be the way in. Delete what you do not need. Fewer plugins means less to patch and less to break.
  • PHP, the database, and the web server. Your host controls these on managed plans. On a cheap unmanaged plan, an old PHP version sits there until you notice the host's email, which may have gone to the designer's old address.
  • The certificate. Not a security patch in the same sense, but an expired certificate trains customers to click through warnings, which is its own problem.
  • Admin accounts. Remove ex-staff and ex-designers. Turn on multi-factor authentication for anyone who can change the site. A patched site with the password "Perth2024!" shared in a group chat is still an open door.

Static sites, the kind with no login and no plugin pile, have a much smaller patch list. That is a good reason to use them for a brochure. They do not remove the need to know who can publish a change, or to renew the domain. They do remove the weekly plugin lottery. If you are choosing a platform, that trade-off belongs in the decision. It is discussed from the design side in website design versus DIY.

A routine that does not rely on memory

Pick a rhythm and write it down. For a typical WordPress business site, a fortnightly check is a reasonable default, with a same-day look when a plugin you use announces a serious hole. The order matters more than the calendar:

  1. Confirm last night's backup exists and is not sitting only on the live server.
  2. Read what is about to update. A major version of a page builder is a different risk from a small security fix.
  3. Update, then look at the homepage, one inner page, and submit the contact form. Check the inbox.
  4. If the site breaks, restore the backup and then decide whether to wait for a fixed release or get help. Do not keep clicking update in the hope it heals.
  5. Note the date, what you updated, and that the form worked. A one-line log is enough. It proves the habit exists.

Automatic updates are reasonable for small security releases on plugins you trust. They are a blunt instrument for a theme that rewrites your layout. Turn autos on for the boring security fixes if you also have backups that restore cleanly. Do not turn them on for everything and then go on leave with nobody watching the site. "Set and forget" is how a bad update sits live all weekend.

Who is allowed to do it

One responsible person or company, not "whoever is in the office". Give them an admin account in their own name, with multi-factor authentication, not a shared "admin" password. Take access off people who have left, including the original developer if they are no longer engaged. If you want this off your plate, that is what website maintenance is for: updates, backups, and a check that the public site still does the basic things. It is cheaper than a cleanup, and it is a different product from hosting alone. Hosting gives the site a place to run. Maintenance is the work of keeping the software current. The split is spelled out in hosting versus building.

What neglected sites tend to become

The common outcomes are dull and damaging. Spam pages get injected and start ranking for rubbish, or the site redirects mobile visitors to a scam while the desktop still looks fine, so you do not notice. Google may flag the site with a warning that scares off real customers. A contact form can be used to send junk through your domain, which then hurts your real email delivery. In worse cases, files are encrypted or defaced and you are restoring from a backup you hoped existed.

Customer data changes the stakes. If the site stores enquiry details, account logins, or orders, a compromise is not only an embarrassment. It can be a privacy incident you need to look at under the Notifiable Data Breaches scheme. That assessment is the business's, with advice if you need it. It is not something a plugin vendor does for you. The practical point is simple: do not store more personal information on the website than you have a reason to keep, and do not leave an old copy of the database sitting in a public folder.

How the break-in usually happens, in more detail than this patching guide, is covered in how websites get hacked. Read that if you want the attack patterns. This article is about the maintenance habit that closes the boring ones.

When it is no longer a patching job

Patching a clean, slightly old site is routine. Cleaning a site that is already compromised is not the same afternoon. Signs you are past routine updates:

  • Google Search Console, the host, or a customer's browser says the site is dangerous or deceptive.
  • You find admin users you did not create, or your own admin password no longer works.
  • Pages you did not write are in the index, or the site jumps to another domain on a phone.
  • The host has suspended you for malware or for sending spam.
  • Updates fail because the site is so old that current plugin versions will not run.

At that point, stop and get a cleanup. Overwriting files at random often leaves the backdoor in place, and the site is reinfected the same week. A proper repair removes the malicious code, resets credentials, patches the hole that let them in, and checks whether the warning in Google needs a review request. That is hacked website repair. After it is clean, the patching habit is what stops the sequel. Repair without maintenance is a repeat invoice.

A small-business standard that is enough

You do not need a security operations centre for a brochure site. You need a short standard and someone who follows it:

  • Only the plugins and the theme you use. Everything else deleted, not just deactivated.
  • Updates on a schedule, with a backup taken first and the form tested after.
  • Multi-factor authentication on admin and on the host login.
  • Unique passwords, stored in a password manager the business controls.
  • A backup that is off the live server, and one tested restore a year so you know it works.
  • The domain, hosting, and admin accounts in the business's name.

If the website also takes payments or holds a lot of customer records, add a conversation about who is watching it and how you would tell customers if it were breached. That is a bigger topic than patching. The patching still has to happen or the bigger conversation is theoretical.

Office IT patching, the PCs and Microsoft 365, is a related habit and a different system. Do not assume the person who updates the laptops is updating the website, or the reverse. Ask both questions. They get missed for the same human reason: nothing looks broken, until it does.

Questions owners ask before they start

If the site looks fine, why patch it?

Visitors and you see the pages. Attackers look at the software underneath: the CMS, the plugins, the theme, and the version of PHP. A site can look normal while it is quietly hosting spam or a fake login. Waiting for it to "look hacked" is waiting too long.

Will updates break my site?

They can, which is why the routine is backup first, update, then check the homepage, a key inner page, and the contact form. Skipping updates because one update once caused trouble is how sites end up a year behind and much harder to fix. The answer is a safer update process, not a freeze.

Are hosted builders safer than WordPress?

A hosted builder patches the platform for you, which removes a whole class of neglected-plugin problems. WordPress is fine when someone keeps core, theme, and plugins current and deletes the plugins you do not use. WordPress with no one responsible for updates is the common small-business incident.

What should we do if we think the site is already compromised?

Stop making it worse. Do not keep logging in from the same infected PC and uploading "clean" copies over the top. Get a backup from before the trouble if you have one, change passwords after the site is clean, and assume the form mail and any stored customer details need a look. Cleaning a live hack is a different job from routine patching.

Need the updates done, or a site that is already in trouble?

Maintenance if it is still clean. Repair if it is not. Tell us which one you think you are in and we will check.

Website maintenance

Stride IT maintains and repairs business websites for Perth and WA clients, and hosts them on Australian infrastructure when hosting is part of the job. If you do not know when the site was last updated, that is already the answer. Contact us with the domain and we will tell you whether it is a maintenance conversation or a cleanup.