Skip to content
Locker Forge

Tutorials

WordPress Security Basics: The Settings Every Site Owner Should Fix Today

WordPress security basics in plain words: back up first, update carefully, set up Wordfence, use a real password with a second lock, and limit login guesses.

WordPressBeginner

11 min read

Locker Forge tutorial card: WordPress Security Basics — the settings every site owner should fix today.
Contents6 sections

Level: Beginner. Time: about one hour, in one sitting. Cost: nothing — everything in this tutorial uses free versions.

1. The update you skipped — and the attack that did not wait

On 28 October 2026, WordPress released version 7.1.4, a security release. It fixed a serious flaw, and the flaw was hiding in the update process itself. It could let an attacker run their own code on a site without even logging in. It affected every WordPress version from 4.7 to 7.1.3. WordPress fixed it the same day they announced it — the new version was ready to download as the news went out.

Wordfence put out a blocking rule about three hours after the release. The first attack reached their rule nine minutes later. Over the first 21 hours, they recorded more than 18,500 requests trying the exploit. This is the part people miss about security updates: the gap between “a fix exists” and “attackers are using it” is not measured in days. It is measured in hours.

That is why this tutorial exists, and why it starts with the fix you already know you should have done. No site is too small to be attacked. The attacks that took advantage of that flaw were automated — the same code probed thousands of sites in a row, and most of them had never heard of the owner.

Priya’s story is the shape of it. She runs a small bakery site in Manchester — eight pages, a contact form, an online order form for collection. Nothing that sounds like a target. She got an email from her host saying her site was sending spam. It turned out someone had got in through an old plugin, hidden a small piece of code, and used her site to send thousands of emails a day. Her customers were not at risk — no orders, no payment details, no addresses were taken. But her site was blocked by Google for a week, and she spent two weekends cleaning it up.

This tutorial closes the five doors that matter most, in the order that matters most: a backup, so you can always undo; updates, done the careful way; one good security plugin, set up properly; a password worth having, plus a second lock on your login; and limits on how many times a stranger can guess that password. That is the whole job, and it takes about an hour.

2. What you need

Four things.

  1. Admin access to your own WordPress site. You need to be able to install plugins, change settings, and update WordPress itself. If you only have an editor account, ask the site owner for an administrator login first.
  2. About one hour, in one sitting. This tutorial is designed to be done in one go. If you stop halfway through, your site is half-protected. That is better than nothing, but not by much.
  3. Your phone, charged, next to you. That is for the second lock on your login in Fix 4. You will need a free authenticator app on it — Google Authenticator or Microsoft Authenticator. Google Authenticator and Microsoft Authenticator are both free, and either one works.
  4. A password manager, or a notebook. You will be changing your password, and you need to write the new one down somewhere safe.

Two plugins appear in this tutorial, and both are free: UpdraftPlus for the backup in Fix 1, and Wordfence for the security plugin in Fix 3. Install them when the tutorial tells you to — do not install them in advance, and do not install any others.

3. The fixes

Fix 1: Back up first, before you touch anything

The first thing to do in a security tutorial is not a security setting at all — it is a backup.

A backup is a copy of your whole site — files and database — saved somewhere you can reach if the site itself breaks. If you already have backups, run a fresh one now. If you have never backed up, follow our backup tutorial first: How to Back Up Your WordPress Site with UpdraftPlus (Before You Touch Anything). It takes about fifteen minutes and costs nothing.

Check that the backup actually happened: go to Settings → UpdraftPlus Backups and look at the Existing Backups section. You should see a fresh backup with today’s date and all five parts listed — Database, Plugins, Themes, Uploads, and Others. If a part is missing, or its size is zero, something went wrong.

One warning, and it is recent: in October 2026, the company behind UpdraftPlus had its own website broken into, and the attackers stole the connection keys for UpdraftCentral, the service that lets you manage backups across sites from one place. The backup plugin itself was not the problem, and the company fixed it with version 1.26.13. Leave UpdraftCentral switched off — you do not need it for this tutorial, and you do not need it for one site.

Once the backup is done, carry on.

Fix 2: Update, but the careful way

WordPress tells you to update, and it is right. But “update everything at once and hope” is not a plan.

  1. Go to Dashboard → Updates. If WordPress itself is out of date, it will say so at the top.
  2. Check your backup is fresh (Fix 1). If it is not, do that first. Updating without a backup is how a small job becomes a big one.
  3. Update WordPress itself first. Then plugins. Then themes.
  4. Do them one at a time. Update one, wait a few minutes, check the front of the site still loads. Then the next.
  5. When you are done, visit the front of the site as a visitor would — open it in a private window, where you are not logged in. If it loads, you are done.

If something breaks, do not panic. It is almost always one plugin, and it is almost always the last one you updated. Deactivate it, check the site works again, and leave it deactivated until its author fixes it. If you cannot get into the dashboard at all, restore the backup from Fix 1 and start again — that is what it is for.

Updating is the single most effective security habit there is. Section 1 shows why: the fix for 7.1.4 existed on 28 October, and the attacks followed within hours — the sites that updated promptly were fine.

Fix 3: Install one good security plugin, and set it up properly

One plugin, done properly, beats three plugins installed and forgotten. Install Wordfence now, because Fixes 4 and 5 use its menus — the password lock and the guessing limit both live inside it. Do not install a second security plugin alongside it — two of them will trip over each other, lock you out, and slow your site down for no extra protection.

  1. Go to Plugins → Add Plugin, search for Wordfence, click Install Now, then Activate.
  2. This tutorial was checked against Wordfence 9.0.2, released on 28 October 2026. Older versions work too. If a step below is not where it says it is, look under Wordfence in the left-hand menu.
  3. When the setup wizard asks for an email, enter yours. That is where security alerts go. If you do not want marketing emails, there is a separate tick-box for those — uncheck it.
  4. When it asks whether to enable the firewall, choose the Optimized setting. That is the setting that protects the site before WordPress itself loads.
  5. Run the first scan: Wordfence → Scan → Start New Scan. Wait for it to finish. If it finds anything, follow the instructions it gives you. If it finds nothing, you are done.

That is the plugin, set up properly. Leave it alone after this, except for updates: Wordfence does not update itself unless you switch on automatic updates for it. In Plugins, find Wordfence and switch on Enable auto-updates — or update it by hand whenever an update appears. It will scan on a schedule, and email you when something needs your attention. Checking it once a month — open Wordfence, glance at the scan results, read any alerts — is enough.

Fix 4: A password worth having, plus a second lock on your login

Your password is the first lock. It needs to be a good one, because automated attacks try the easy ones first — and they try them by the thousand.

  1. Go to Users → Profile. If you log in as someone else, go to Users → All Users and click their name.
  2. Under Account Management, click Set New Password and click Generate Password. WordPress will suggest a long, random password. Use it, or type your own — at least 16 characters, a mix of letters, numbers and symbols, and nothing that appears in a dictionary.
  3. Write it down in your password manager or your notebook. Then click Update Profile.
  4. Log out and log back in with the new password, to be sure it works. If it does not, use the password reset link on the login page — you will not be locked out for long.

Now the second lock. Two-factor authentication, or 2FA, means that even if someone guesses your password, they still cannot get in — they would also need a code from your phone, which changes every 30 seconds. Wordfence, which you installed in Fix 3, includes 2FA for free.

  1. Install an authenticator app on your phone. Google Authenticator and Microsoft Authenticator are both free. Open the app.
  2. Go to Wordfence → Login Security, then click Two-Factor Authentication.
  3. Click Activate. Wordfence will show you a square code — a QR code — and a list of recovery codes.
  4. Scan the QR code with the app. Type the six-digit code the app shows into Wordfence and click Activate.
  5. Save the recovery codes somewhere safe — your password manager, or a piece of paper in a drawer. They are your way back in if you lose your phone. Do not save them on your computer’s desktop, and do not email them to yourself.

Log out and log back in once, to be sure the second lock works. WordPress will ask for your password, then for a code from the app. That is the whole point.

Fix 5: Limit how many times a stranger can guess your password

Automated attacks do not guess once — they guess thousands of times, one password after another, as fast as the site will let them. The fix is to set a limit: after a few wrong guesses, lock the door for a while.

Wordfence does this, under the name brute-force protection. “Brute force” means trying every password until one works, by force of numbers.

  1. Go to Wordfence → All Options, then scroll to Brute Force Protection.
  2. Set Lock out after how many login failures to 5.
  3. Set Lock out after how many forgot password attempts to 5.
  4. Set How long is an IP address blocked when it breaks a rule to 4 hours.
  5. Scroll to the bottom and click Save Changes.

That is it. A real person who mistypes their password five times in a row will be locked out for four hours — which is annoying, but rare, and they can use the password reset link instead. An automated attack that tries thousands of passwords will be locked out after five.

4. The four most common mistakes — and what to do instead

MistakeWhat happensWhat to do instead
Updating with no backupOne bad update takes the site down, and there is no easy way back.Back up first. That is Fix 1.
Installing a second security plugin “for extra safety”The two plugins fight, lock you out, and slow the site down.One security plugin, set up properly. That is Fix 3.
Using “admin” as your usernameAttackers try “admin” first, before any other username.Create a proper named administrator account, then delete or demote the “admin” one.
Switching on UpdraftCentral to manage backups across sitesYour backup keys are stored on Updraft’s website — which was broken into in October 2026.Leave it switched off. Back up each site on its own.

5. If something goes wrong

Three problems, three fixes.

  • You are locked out. Wait out the lockout from Fix 5 — it is four hours at most. Or use the password reset link on the login page. If you are locked out of the whole site, your host can disable Wordfence for you, or you can rename the Wordfence folder by FTP.
  • You lost your phone, or the app will not give you a code. Use one of the recovery codes you saved in Fix 4. If you did not save them, your host can disable Wordfence’s two-factor check for you, or you can rename the folder by FTP.
  • An update broke the site. Restore the backup from Fix 1, then update one plugin at a time until you find the one that broke it. Leave that one deactivated until its author fixes it.

If none of that works, ask for help — your host’s support team, or a WordPress developer. Say what you did, in order, and what you see now. That is enough for someone to help you.

6. What you have done — and what to do next month

You have done the five fixes. Your site is backed up, it is up to date, one good plugin is standing guard, your password is worth having, and strangers can only guess it five times before they are locked out.

Keep it that way. Once a month, spend ten minutes on it: back up first, update carefully, let one good plugin stand guard, use a password worth having plus a second lock, and limit the guessing. Priya, from Section 1, does exactly this — she runs through Fix 2 and glances at Wordfence once a month, on the first Sunday. Her site has not been broken into since.

WordPress version checked: 7.1.4, released 28 October 2026. Wordfence version checked: 9.0.2, released 28 October 2026. UpdraftPlus version checked: 1.26.14, released 26 October 2026.


Keep learning: How to Back Up Your WordPress Site with UpdraftPlus (Before You Touch Anything) — the backup tutorial this one builds on.

Newsletter

Get the next tutorial in your inbox

One useful email when something new ships. Practical build notes, no fluff, unsubscribe any time.

No spam. Your address is never shared.