The Developer's EdgeNovember 20, 2026 · 6 min read

WordPress Security Checklist for Small Business Sites

A WordPress security checklist for small business owners: updates, PHP, backups, 2FA, user roles, plugins and login limits, each tied to official docs.

M

Murad Raza

Freelance Full-Stack Developer

WordPress Security Checklist for Small Business Sites

A WordPress security checklist for a small business site is short. Keep WordPress, plugins and themes updated, run a supported PHP version, keep backups in more than one place, put two-factor authentication on every admin account, give people only the access they need, delete what you do not use, and slow down login guessing. None of it needs a big budget, just someone who owns it every week.

Most of the client sites I build are WordPress, and I have been building them since 2022. I have not run a security study on those sites, so this guide does not quote numbers from client work. Each item comes from official WordPress and PHP documentation or a published security report, linked inline so you can check it.

Key Takeaways

  • Plugins carry most of the risk: Patchstack found that 91% of new WordPress vulnerabilities in 2025 were in plugins and 9% in themes.
  • Turn on auto-updates for trusted plugins and run PHP 8.3 or newer, the version WordPress recommends.
  • Keep regular backups of the database and files, stored in more than one place.
  • WordPress core has no two-factor authentication, so add it to every administrator account.
  • This is a few minutes a week plus a quarterly review, not a one-off project.

Why plugins are the main risk

Patchstack's State of WordPress Security in 2026 report counted 11,334 new vulnerabilities in the WordPress ecosystem during 2025. Of those, 91% were in plugins and 9% in themes, while WordPress core had only 6, all low priority. Every plugin is separate code from a separate developer, and each one is another thing that needs patching.

The WordPress security checklist

1. Keep core, plugins and themes updated

The official Hardening WordPress guide says to "always keep up to date with the latest version of WordPress" and to make sure plugins are always updated. Minor and security releases of core update automatically on most sites by default, according to the Upgrading WordPress documentation. Plugins and themes do not, unless you opt in. Since WordPress 5.5, the Plugins screen has an "Automatic update" column with a link to enable auto-updates plugin by plugin.

Turn it on for well-maintained plugins. For anything that touches checkout, such as WooCommerce payment plugins, update by hand after a backup so you can place a test order straight away.

2. Run a supported PHP version

WordPress recommends PHP 8.3 or greater. PHP only patches branches that are still supported, and the PHP supported versions page shows 8.2 as the oldest, with security support ending on 31 December 2026. A branch past its end of life may be exposed to unpatched security vulnerabilities. Check your version under Tools, Site Health, Info, Server, and ask your host to move you up. I wrote about one recent patch in this WordPress PHP security update guide.

3. Keep backups you can actually restore

The WordPress backup guide splits a backup into two parts, the database and the files, and says to keep copies "stored in different locations". It suggests weekly backups for small sites, daily for busy ones, and a backup "always before an upgrade". Keep at least one copy outside your hosting account. If the server is compromised or the host closes your account, a backup on that same server goes with it. Test a restore on a staging copy once a year, because a backup you have never restored is a guess.

4. Turn on two-factor authentication

"WordPress core does not ship 2FA; it must be added via a plugin or SSO/IdP," says the official guide to brute force attacks, which recommends 2FA for all administrator accounts. The two-step authentication page lists plugins such as Two-Factor, Duo and Wordfence. Pair it with a strong, unique password for every account.

5. Give people only the access they need

According to the Roles and Capabilities documentation, an Administrator has access to all the administration features, including installing plugins and editing theme files. An Editor can publish and manage posts, including other people's, without those code-level powers. Your content writer or marketing assistant almost always needs Editor or Author, not Administrator. Remove accounts for staff and agencies who have left. Fewer admins means fewer passwords that unlock everything.

6. Delete plugins and themes you do not use

The hardening guide is direct: "if you are not using a specific plugin, delete it from the system." A deactivated plugin still leaves its files on the server, so delete it. Remove spare themes too, keeping one default theme as a fallback. Before installing anything new, check its last update date and active installs on its wordpress.org page.

7. Slow down login guessing

Bots try passwords on the login page constantly. The brute force guide recommends rate-limiting login attempts at the edge (a firewall or CDN) or on the web server, and says a security plugin can throttle attempts if your host does not. It also suggests protecting or disabling XML-RPC if you do not need it.

8. Turn off the dashboard file editor

Add define( 'DISALLOW_FILE_EDIT', true ); to wp-config.php. The hardening guide documents this constant: it removes the theme and plugin editor from the dashboard, so a stolen admin login cannot be used to paste code into your site from the browser. The same guide says to lock down file permissions as much as possible.

How often to run each check

TaskHow often
Review pending updatesWeekly
Database and file backupsWeekly for small sites, daily for busy sites and shops
Check the PHP versionEvery few months
Review user accountsQuarterly, and whenever someone leaves
Remove unused plugins and themesQuarterly
Test a restoreOnce a year

Backup timings follow the WordPress guide. The rest are sensible defaults, not official rules.

When to hand it off

If nobody in the business owns this routine, that gap is the real risk. I break down typical prices in what website maintenance costs per month, and my WordPress maintenance service covers updates, backups and checks like the ones above. If your site has already been hacked, restore a clean backup, change every password, update everything and find how they got in, then work through this list.

Frequently asked questions

01Is WordPress secure enough for a small business site?
Yes, when it is maintained. Patchstack found only 6 vulnerabilities in WordPress core in 2025, all low priority. Most of the risk comes from outdated plugins and themes, which is where Patchstack found nearly all new vulnerabilities.
02Do I need a security plugin?
Often, yes, because WordPress core does not include two-factor authentication. If your host or CDN does not rate-limit logins, a security plugin can also throttle login attempts.
03Should I turn on auto-updates for every plugin?
For most well-maintained plugins, yes. For payment, checkout or booking plugins, update manually after a backup so you can test the key flow right away.

Need this fixed on your site?

I Build Websites That Work as Hard as You Do

Start a project

Have a project in mind?
Let's build it right.

Two project slots open right now. Tell me what you're building and I'll reply within two business days.