Skip to content

Website security: how to protect a WordPress site in 2026

Website security comes down to a few habits: updates, a safe login, tested backups, HTTPS and monitoring. A 2026 checklist and what to do after a hack.

By K!K!Design

9 min read

Published on

Updated:

A round spacecraft pressure hatch with a titanium and gold locking ring

Website security is not one product but a handful of habits: update promptly, protect the login with a long password and a second factor, keep backups you have actually restored, and watch what happens on the site. Most attacks on small business sites are automated: bots crawl the web looking for outdated plugins and weak passwords, and these habits close exactly the doors they use. If you would rather someone else kept them, that is what our website maintenance does.

In short

  • Updates are your first line of defence. In 2025, 91 % of new WordPress vulnerabilities were in plugins, and the most targeted ones were exploited a median of five hours after disclosure (Patchstack).
  • Protect the login with length and a second factor, not with complex rules and monthly password changes.
  • A backup you have never restored is a hope, not a backup. Keep a copy off the server and test the restore.
  • HTTPS is essential, but it only protects data in transit. It does nothing against a vulnerable plugin.
  • If you are hacked, delete nothing. Change the passwords, call your developer and follow the first-hour steps below.

What is website security?

Website security means protecting a site, its data and its visitors from online threats: break-ins, malicious code, phishing, stolen passwords and software vulnerabilities. Security people sum up the goal in three words: confidentiality (outsiders cannot see the data), integrity (nobody changes it without permission) and availability (the site is up when customers need it).

For the owner of a company site or an online shop, that translates simply. Only you and your team get into the admin area. The site never sends spam or malware in your name. And it opens when a customer looks for it.

Why does website security matter?

A hacked site costs money, time and trust, and sometimes has legal consequences:

  • You lose customers. Google can show a red warning that the site is dangerous, and the browser stops visitors before they reach the page. Few click through.
  • You lose visibility. Infected pages drop out of search, and Search Console flags the site in its Security issues report until it has been cleaned and reviewed.
  • Data leaks. If customers’ personal data leaks through the site, Article 33 of the GDPR (and of the UK GDPR) requires the controller to notify the supervisory authority within 72 hours (the ICO in the UK), unless the breach is unlikely to put people at risk.
  • Repairs are expensive. Cleaning a hacked site takes more time and money than prevention, and sometimes the site has to be rebuilt.

How big is the threat to WordPress sites?

Patchstack’s annual report, State of WordPress Security in 2026, counted 11,334 new vulnerabilities in the WordPress ecosystem in 2025, 42 % more than the year before. 91 % were in plugins and 9 % in themes; WordPress core had six, all low risk. For 46 % of them, the developer had not shipped a fix by the time they were made public.

The practical conclusion: WordPress core is well guarded, and the risk comes from add-ons. Every plugin is a door that someone has to keep locked.

Where attacks get in, and what stops them

This table is the map we start every site review with.

Way inWhat happensWhat stops it
An outdated plugin or theme with a known vulnerabilityA bot uploads a malicious file or creates itself an admin accountUpdates within days, removing unused plugins, a web application firewall (WAF)
A weak or reused passwordA bot tries thousands of passwords, or uses ones leaked from other sitesA long unique password, a password manager, two-factor login, limited login attempts
Too many administratorsA former employee’s or contractor’s account opens the whole siteLeast privilege, regular user reviews, deleting old accounts
Weak hosting or an old PHP versionThe breach is in the server, not the siteHosting on a supported PHP version, a separate account per site, SFTP instead of FTP
Forms and commentsSpam and code injection attemptsInput validation, bot protection, comments switched off if unused
No backupEvery attack or mistake becomes permanentAutomatic off-server backups and a tested restore

How to protect your website: 7 measures

1. Use HTTPS everywhere

HTTPS encrypts data between the visitor’s browser and the server, so nobody in between can read or alter it. It runs on a TLS certificate, the successor to SSL (most people still say “SSL certificate”), and most hosts issue one free, for example through Let’s Encrypt.

Two things are new. First, since 15 March 2026 certificates are valid for at most 200 days, falling to 100 days from 15 March 2027 and 47 days from 15 March 2029 (a CA/Browser Forum decision of April 2025), so renewal has to be automatic. Second, HTTPS protects the data in transit, not the site itself: a plugin exploit walks straight past the padlock.

2. Keep the software up to date

Outdated software is the most common way in. Update WordPress core, the theme, the plugins and the server’s PHP version. WordPress installs minor core releases, the ones with security fixes, on its own; plugins and themes are your call.

  • Apply security fixes within days, and the same day for a serious vulnerability.
  • Test major updates on a staging copy first, especially on a shop.
  • Delete plugins and themes you do not use. A deactivated plugin that still sits on the server can still be attacked.
  • Never install “free” copies of premium themes and plugins from dubious sites: they often carry hidden malware.
  • Check that your PHP version still receives security fixes (php.net lists them).

3. Use long passwords, not complex rules

The old advice, including in the earlier version of this article, was upper and lower case, digits, symbols and a new password every few months. Today’s guidance says otherwise. NIST SP 800-63B (revision 4, 2025) requires a password that is the only factor to be at least 15 characters long; systems should not impose character-type rules or scheduled changes, and a password is changed when there is evidence it has leaked. New passwords are checked against lists of common and breached passwords. The UK’s National Cyber Security Centre makes the same point with its “three random words” advice.

In practice: a phrase of a few random words, different for every site, kept in a password manager (the one built into your browser is fine).

4. Limit access

  • Two-factor login (an authenticator app or a passkey) for every administrator.
  • Least privilege. Authors write posts, editors edit them, and only one or two people are administrators.
  • Limited login attempts, and no user called “admin”.
  • One account per person, including each outside contractor, deleted when the work ends.
  • Close the entry points you do not use, for example XML-RPC if no app relies on it.

5. Back up, and test the restore

The 3-2-1 rule applies to websites too: three copies, on two different media, one of them off the server. A backup stored on the same server disappears with it.

  • Run backups automatically: daily for a shop, and at least weekly for a company site that rarely changes.
  • Keep several weeks of history: an infection is often found days after the break-in.
  • Every few months, restore a backup to a staging copy. Only then do you know it works.

6. Add a firewall and monitoring

A web application firewall (WAF) blocks known attacks before they reach the site. In our care plans we use Wordfence: a firewall, login protection and two-factor login for administrators. Your host’s protection helps, but it is not enough on its own: in a Patchstack test of hosting companies, they blocked only 26 % of attacks on WordPress vulnerabilities.

Also watch:

  • whether the site is up, with an alert when it goes down;
  • changes to core, theme and plugin files;
  • the Security issues report in Google Search Console;
  • when the domain and the certificate expire.

7. Keep less data and harden the server

What you do not store cannot leak. Collect no more in your forms than you need, and delete old enquiries on a schedule. On the server: security headers (HSTS, Content-Security-Policy, X-Content-Type-Options), file editing disabled in the admin area, and a database user with only the rights it needs.

Hacked? What to do in the first hour

  1. Delete nothing. Traces in the files and logs show how the attacker got in.
  2. Change the passwords for the admin area, hosting, SFTP, the database and e-mail, ideally from another device. Turn on two-factor login wherever it is missing.
  3. Limit the damage. If the site is sending spam or redirecting visitors, ask your host to suspend it for now, or switch on a maintenance page.
  4. Call your developer, or us on +359 884 615 302. The sooner the hole is closed, the less there is to clean.
  5. Check Search Console for alerts under Security issues and Manual actions.
  6. Restore a clean backup only once the hole has been found. Otherwise the attacker walks back in through the same door.
  7. If personal data has leaked, decide with your lawyer whether you must notify the supervisory authority within 72 hours (Article 33) and the people affected.

Once the site is clean, request a review in Search Console so Google lifts the warning.

How we protect the sites we look after

The sites of Tandem Export and Reha Bul run on our own WordPress theme and our own plugin, with no page builder. That is not a matter of taste: fewer third-party plugins means fewer doors to lock and fewer updates that can break something.

As with every site in our care, updates go to a staging copy first and only then to the live site. That is how Tandem Export’s catalogue gets new theme versions and new features without interrupting the trade customers who order through it. Backups run on a schedule, and the admin login sits behind a firewall and two-factor login.

Frequently asked questions

How do I know if my website has been hacked?

Common signs are admin users or pages you did not create, redirects to unfamiliar sites, spam sent from your domain, a site that suddenly slows down, and a warning from Google in Search Console or in the browser. Sometimes there is no visible sign at all, which is why our care plans also watch for file changes.

Is an SSL certificate enough to make a site secure?

No. The certificate (TLS today) encrypts data on its way between the visitor and the server. It does not protect against a vulnerable plugin, a weak password or a leaked account. You still need updates, a protected login, backups and monitoring.

Do I need a WordPress security plugin?

A firewall such as Wordfence blocks known attacks and protects the login, which is why we use it in our care plans. It does not replace updates: a security plugin on top of outdated plugins is an alarm on an open door.

How often should I update WordPress and its plugins?

Check at least once a week and apply security fixes within days. For the most targeted vulnerabilities of 2025, the first attacks arrived a median of five hours after disclosure (Patchstack), so a serious fix should not wait for next week.

What does website security cost?

It depends on the kind of site, its plugins and integrations, and the response time you need: a shop needs more checks than a brochure site. Our care starts from €25 a month (excl. VAT). Our pricing page has the starting prices.

More from the blog

All articles

Want someone to keep an eye on your site?

Our website maintenance covers updates tested on a staging copy, backups, a firewall, monitoring and emergency help within a response time written into the contract. Like mission control, we watch the instruments so there are no fires to put out. We start with a review and tell you what we find.

Start a project Website maintenance +359 884 615 302