Blog
Your Website Is Software: Updates, Plugins and Who Can Log In
Most owners think of the company website as marketing. It's the brochure, the contact form, maybe the careers page. Somebody built it a few years ago, and it mostly just sits there.
But a website isn't a brochure. It's software running on a computer connected to the internet around the clock, and anyone in the world can reach it. If it runs on WordPress or another content management system (CMS, the software that lets non-programmers edit pages), it needs the same care as any other system: updates, sensible logins and someone paying attention.
This post covers the three things that matter most for a typical small-business site: updates, plugins, and who can log in.
Why anyone would bother with your site
Owners often say, "We're too small to be a target." For websites, that's the wrong way to think about it. Most website attacks aren't aimed at a particular company. Automated tools scan huge numbers of sites looking for a known weakness, such as an outdated plugin or a weak admin password, and they take over whatever they find.
What they do next varies. They might inject spam links, redirect visitors to scams, plant malware for visitors to download, or use your site to send email. Your name and your domain end up attached to it. Search engines and browsers may flag the site as dangerous, and customers see a red warning page where your homepage used to be.
Updates: the core, the theme, the plugins
A WordPress site is made of three layers, and each one gets updates:
- The core: WordPress itself.
- The theme: the design layer that controls how the site looks.
- Plugins: add-ons that provide features such as contact forms, sliders, search engine tools and online stores.
Security fixes arrive in all three. WordPress can now update itself and its plugins automatically, and you can turn that on plugin by plugin, as described in the WordPress documentation. For most small-business sites, automatic updates for minor and security releases are the right default.
When I ran IT at a company of about 200 people, the websites that got into trouble were rarely the ones under active development. They were the ones nobody was assigned to. The agency that built the site had moved on, the marketing person who knew the login had left, and the site sat unpatched for a year or two while it kept quietly working.
Plugins: fewer is safer
Plugins are where most WordPress weaknesses live. Not because plugins are bad, but because there are so many of them, written by so many different people, with very different levels of care and support.
A few rules of thumb:
- Fewer plugins means fewer doors. Every plugin is code someone else wrote, running on your site. If you're not using it, delete it. Deactivated plugins can still be a risk if their files stay on the server.
- Prefer actively maintained plugins. In the WordPress plugin directory, each plugin shows when it was last updated and whether it's been tested with recent versions of WordPress. A plugin that hasn't been touched in years is a warning sign.
- Watch for abandoned or closed plugins. Sometimes a plugin is closed in the directory, occasionally for security reasons. If you use one, ask your developer about a replacement.
- Be careful with "nulled" plugins. These are pirated copies of paid plugins, and they're a common way malicious code gets onto sites.
The same thinking applies to themes. Keep one active theme and its parent if it uses one, and delete the rest.
Who can log in
The admin login is the front door of your website. Think through who has a key.
Count the administrators. WordPress has several roles. Administrators can do everything, including installing plugins and adding other users. Editors can manage content but not the site's machinery. Most people who update the site need editor access, not administrator access. In many small-business sites I've looked at, the list of administrators includes people who left years ago and agencies that no longer work with the company.
Remove old accounts. Former employees, former agencies and former freelancers should be deleted or downgraded as soon as the relationship ends.
Avoid the obvious usernames. An account literally named "admin" is the first one automated tools try.
Use strong passwords and MFA. WordPress doesn't require two-factor authentication (MFA) by default, but reputable plugins add it, and many hosting companies offer it at the hosting level too. Every administrator account should have it.
Limit what an admin can change from the dashboard. WordPress has a setting that turns off the built-in code editor, so a stolen admin login can't be used to edit the site's code directly. The official hardening guide explains this and other settings for your developer.
Who owns the website?
This is the leadership question underneath all of the above. Someone has to own the site: not to build it, but to make sure updates happen, accounts are current and problems get noticed. That might be your marketing lead, your IT provider or a web agency on a small monthly maintenance plan. What matters is that it has a name next to it.
Make sure the company, not an individual or an agency, holds the master logins for the site, the hosting account and the domain name. If the relationship with the agency ends, you shouldn't have to ask permission to get into your own website.
Other CMS platforms
The same principles apply to Drupal, Joomla and other self-hosted systems. Hosted website builders, where the platform runs the software for you, take care of most updates themselves. With those, your main job is the logins: strong passwords, MFA and removing people who no longer need access.
What to do Monday morning
- Find out who owns the website, who holds the admin, hosting and domain logins, and make sure the company controls all three.
- Ask for the list of administrator accounts. Remove anyone who's left and downgrade anyone who only edits content.
- Turn on MFA for every administrator and check that no account is named "admin."
- Ask your developer or host whether automatic updates are on for WordPress, the theme and the plugins, and when the site was last fully updated.
- Get a list of installed plugins, and delete anything unused, abandoned or pirated.