All articles Maintenance

WordPress Security: A Practical Checklist to Protect Your Site (2026)

Why WordPress sites get hacked and what actually protects them: updates, plugins, logins, backups, hardening, firewall and monitoring, with a checklist you can work through in an afternoon.

WP Beekeeper Team · 13 min read
Laptop behind a large shield with a keyhole and a padlock: WordPress security

WordPress runs a large part of the web, which makes it the most attractive target for automated attacks. Bots scan millions of sites every day, looking for one thing: a plugin, theme or login that is easy to break. They do not care whether your site belongs to a global brand or a small bakery.

The good news is that WordPress security is not mysterious. Most hacked sites fall to the same handful of weaknesses: outdated plugins, weak or reused passwords, missing backups and no one watching. This guide walks you through what actually protects a WordPress site in 2026, in order of impact, with a checklist you can work through in an afternoon.

Key takeaways

  • Plugins are the biggest risk: according to Patchstack, 91% of new WordPress vulnerabilities in 2025 were found in plugins, and only six in WordPress core.
  • Updates are the most effective protection, but not enough on their own: 46% of vulnerabilities had no fix yet when they were made public.
  • Use fewer plugins, only from trusted sources, and remove anything you do not use.
  • Protect logins with unique passwords, two-factor authentication and as few administrators as possible.
  • Keep backups outside your server and test that you can restore them.
  • A firewall and monitoring close the gap between a new vulnerability and the update that fixes it.

Why WordPress sites get hacked

WordPress core itself is well reviewed and rarely the problem. The risk sits in the thousands of plugins and themes built by different developers. The Patchstack State of WordPress Security 2026 report counted 11,334 new vulnerabilities in the WordPress ecosystem in 2025, 42% more than the year before. 91% were in plugins, 9% in themes, and only six, all low priority, in WordPress core.

Two more numbers from the same report explain why speed matters. For the most heavily exploited vulnerabilities, the weighted median time to mass exploitation was five hours. And 46% of vulnerabilities had no fix from the developer when they were disclosed. In other words: updating quickly is essential, and for some gaps there is nothing to update yet.

Attackers rarely target you personally. Automated scripts try known vulnerabilities, leaked passwords and default settings on every site they find. Once inside, they use your site for spam pages, redirects, phishing or malware, often without you noticing for weeks.

The WordPress security checklist at a glance

MeasureProtects againstEffort
Update core, plugins and themes regularlyKnown vulnerabilities, the most common way inLow, if routine
Remove unused and abandoned plugins and themesCode nobody maintains anymoreLow
Unique passwords and two-factor authenticationStolen and guessed passwordsLow
Few administrators, correct user rolesDamage from a single hacked accountLow
Backups outside the server, testedLosing everything after an attack or errorMedium, once set up
HTTPS everywhereIntercepted logins and dataLow
Disable the file editor, protect wp-config.phpAttackers editing code from the dashboardLow
Current PHP version and a solid hostServer-side vulnerabilitiesLow to medium
Web application firewall (WAF)Attacks on vulnerabilities that are not patched yetMedium
Monitoring of uptime, files and Search ConsoleNoticing an attack lateLow, if automated

1. Keep WordPress, plugins and themes updated

Most successful attacks use vulnerabilities that already have a fix. The site was simply never updated. WordPress installs minor and security releases of core automatically on most sites, but plugins and themes are your responsibility.

  • Check for updates at least weekly, and install security updates as soon as they appear.
  • Update in a sensible order and with a backup first. Our guide on updating WordPress safely explains how.
  • Do not ignore premium plugins and themes. They often update outside the WordPress dashboard and are easy to forget, especially when a licence has expired.
  • Check your pages after updating, so a broken layout or form does not go unnoticed.

2. Fewer plugins, from trusted sources

Every plugin is code that runs on your site and can contain a vulnerability. Fewer plugins means less attack surface and fewer updates to keep track of.

  • Delete plugins and themes you do not use. Deactivated is not enough: the files stay on the server and can still be attacked.
  • Replace plugins that have not been updated for a year or more. If the developer is gone, nobody will fix the next vulnerability.
  • Only install plugins from WordPress.org or the developer’s own website. Never use “nulled” premium plugins from download sites: they very often contain malware.
  • Before installing, check active installs, last update and reviews.

3. Secure logins and user accounts

The second big way in is the login. Bots try leaked passwords and common combinations on wp-login.php all day long.

  • Unique, long passwords for every account, generated and stored in a password manager. Never reuse a password from another service.
  • Two-factor authentication for every administrator and editor. Even a stolen password is then not enough.
  • Limit login attempts or use a security plugin or host feature that blocks repeated failed logins.
  • No user called “admin”, and do not show your login name as the author name.
  • Few administrators. Give editors, authors and agencies only the role they need, and remove accounts of people who no longer work with you.
  • Check users regularly. An unknown administrator is one of the clearest signs of a hacked site.

4. Backups you can actually restore

A backup does not stop an attack, but it decides whether an attack costs you an afternoon or your whole website. A usable backup:

  • contains files and database,
  • is stored outside your web server, so an attacker or a server failure cannot destroy it along with the site,
  • exists in several versions, because an infection is often discovered days or weeks later,
  • has been restored at least once as a test.

Our WordPress backup guide explains how to set this up.

5. HTTPS everywhere

Your site should load only over HTTPS, including the login and the admin area. Most hosts include a free SSL certificate. Check that HTTP redirects to HTTPS, that the certificate renews automatically and that no page shows a mixed content warning.

6. Harden WordPress settings

A few settings make life much harder for an attacker who gets a foot in the door. The most useful one disables the theme and plugin file editor in the dashboard, so nobody with an admin login can change PHP code from there. Add this line to wp-config.php:

define( 'DISALLOW_FILE_EDIT', true );
  • Security keys (salts): after a suspected break-in, generate new keys in wp-config.php. This logs out every user, including an attacker with a stolen session.
  • File permissions: limit write access to what WordPress needs. Usually that means 755 for folders and 644 for files, with wp-config.php stricter if your host allows it.
  • Use SFTP, not plain FTP, and change hosting, database and FTP passwords from time to time.
  • Hiding the login URL reduces bot noise, but it is not real protection. Treat it as a bonus, not a replacement for strong passwords and two-factor authentication.

The official Hardening WordPress guide lists these and further measures in detail.

7. A current PHP version and a solid host

Security does not end at WordPress. Your server runs PHP, and old PHP versions no longer receive security fixes. PHP 8.2 reaches the end of its security support on 31 December 2026, and 8.1 and older are already unsupported. Our guide on updating the PHP version in WordPress shows how to switch safely. A good host also isolates your site from other customers, keeps the server updated and offers server-side backups and malware scanning.

8. A web application firewall

Because almost half of vulnerabilities are public before a fix exists, updates alone leave a gap. A web application firewall (WAF) filters malicious requests before they reach WordPress, and some services apply “virtual patches” that block a known attack even when the plugin is not fixed yet. You can use a WAF from your host or CDN, or a security plugin with firewall features. One firewall is enough: several security plugins on the same site mostly slow it down and get in each other’s way.

9. Switch off what you do not need

  • XML-RPC is an old interface that bots like to use for password guessing. If you do not use the WordPress mobile app, Jetpack or a service that needs it, it can be blocked, usually with a setting at your host or in a security plugin.
  • User registration: under Settings → General, “Anyone can register” should be off unless you run a membership site, and the default role for new users should never be Administrator.
  • Old test and staging installations on the same server are forgotten WordPress sites that never get updated. Delete them.
  • Comment and form spam is not a direct security problem, but spam protection keeps bots away from your forms.

10. Monitoring: notice problems early

Many site owners learn about a hack from a customer or a Google warning, weeks later. Monitoring shortens that time:

  • Uptime monitoring tells you when your site is down or shows an error.
  • Visual checks after updates show defacements and broken pages.
  • File change monitoring or regular malware scans spot injected code.
  • Google Search Console shows a warning under Security issues if Google detects hacked content. Register your site there if you have not yet.
  • Check the user list and the list of installed plugins regularly for anything you did not add.

Who is responsible for what?

Security problems often slip through because everyone assumes someone else is taking care of them. This is the usual split:

AreaYour hostYou or your maintenance service
Server, operating system, networkYesNo
PHP versions available on the serverYesChoosing and switching the version for your site
WordPress core, plugins and themesNo (some managed hosts update core)Yes
User accounts, passwords, two-factor authenticationNoYes
BackupsOften server backups, sometimes only a few days backYour own backups outside the server
FirewallOften a basic firewall or WAFA WordPress-specific firewall or security plugin, if the host has none
Checking that the site works after changesNoYes

How to set up two-factor authentication

WordPress does not include two-factor authentication out of the box, but it takes about ten minutes to add:

  1. Install a two-factor plugin from WordPress.org, or use the two-factor feature of your security plugin if you already have one.
  2. Install an authenticator app on your phone, for example the one from your password manager, Google Authenticator or Microsoft Authenticator.
  3. In your WordPress profile, scan the QR code with the app and confirm with the first code.
  4. Save the backup codes in your password manager. Without them, a lost phone can lock you out.
  5. Make two-factor authentication mandatory for all administrators and editors, not optional.

A 15-minute monthly security routine

Once the basics are in place, a short monthly routine keeps your site in good shape:

  1. Check that the last backups ran and are stored outside the server.
  2. Install pending updates, with a backup first, and check your main pages afterwards.
  3. Look at the user list and remove accounts that are no longer needed.
  4. Look at the plugin list and remove anything unused or no longer maintained.
  5. Check Google Search Console for security issues and new errors.
  6. Check that the SSL certificate is valid and renews automatically.
  7. Note the PHP version and plan the upgrade before support ends.

WP Beekeeper takes over the backups, the updates, the page check afterwards and the uptime and SSL monitoring automatically, so the rest of the routine only takes you a few minutes.

Common WordPress security myths

MythReality
“My site is too small to be hacked.”Bots attack automatically and do not check how big you are, only what is outdated.
“A security plugin is enough.”A plugin helps, but it does not replace updates, strong logins and backups.
“Hiding wp-admin makes my site secure.”It cuts down bot noise. It does not stop an attack on a vulnerable plugin.
“Premium plugins are safer.”Premium code has vulnerabilities too, and is often updated less reliably because licences expire.
“My host takes care of security.”Hosts protect the server. Plugins, themes, users and passwords are your responsibility.

What to do if your site has already been hacked

If you see spam pages, strange redirects, unknown admin users or a warning from Google or your host, act quickly but calmly. Our guide on what to do if your WordPress site is hacked takes you through it step by step. If you would rather hand it over, our hacked site help starts from 399 euros, the same day, seven days a week.

WordPress security for agencies

An agency with dozens of client sites faces every risk above many times over: hundreds of plugins, many logins, and one vulnerable plugin that is installed on twenty sites at once. What helps most is standardisation: the same small set of trusted plugins on every site, one place where all updates and vulnerabilities are visible, two-factor authentication for every team account, and automated backups and monitoring for all sites. Our offer for agencies is built around exactly that.

Not sure where your site stands?Our Security Audit checks for malware and reviews user accounts, file permissions and login hardening. You get one clear report with what to fix, at a fixed price from 79 euros.

Security Audit →

WordPress security checklist

  • WordPress, plugins and themes updated, security updates installed promptly
  • Unused and abandoned plugins and themes deleted
  • Only plugins from WordPress.org or the developer, no nulled software
  • Unique passwords from a password manager for every account
  • Two-factor authentication for administrators and editors
  • Login attempts limited, no user called “admin”
  • Few administrators, old accounts removed
  • Backups outside the server, several versions, restore tested
  • HTTPS everywhere, certificate renews automatically
  • File editor disabled with DISALLOW_FILE_EDIT
  • Current PHP version
  • Web application firewall active
  • Uptime, visual checks and malware scans running
  • Site registered in Google Search Console

Sources and further reading

Frequently asked questions

How do I make my WordPress site secure?

Keep WordPress, plugins and themes updated, remove what you do not use, protect logins with unique passwords and two-factor authentication, keep tested backups outside the server, use HTTPS, add a web application firewall and monitor your site.

Is WordPress secure?

WordPress core is well maintained and rarely the cause of a hack. According to Patchstack, only six of 11,334 new vulnerabilities in 2025 were in core. The risk lies mainly in plugins, themes, weak passwords and missing updates.

Do I need a security plugin?

A security plugin or a firewall from your host is useful, especially for blocking login attacks and unpatched vulnerabilities. But it does not replace updates, strong logins and backups. Use one solution, not several at once.

How often should I update WordPress plugins?

Check at least once a week and install security updates as soon as they appear. Make a backup first and check your pages afterwards.

What is two-factor authentication in WordPress?

Two-factor authentication asks for a second proof at login, usually a code from an app on your phone, in addition to the password. A stolen password alone is then not enough to log in.

Should I change the WordPress login URL?

It reduces automated login attempts, but it is not real protection. Strong passwords, two-factor authentication and limited login attempts matter far more.

How do I know if my WordPress site has been hacked?

Typical signs are unknown admin users, spam pages in Google, redirects to other sites, warnings from your host or browser, and a security warning in Google Search Console. Our guide on hacked WordPress sites explains what to do next.

Conclusion

WordPress security is less about clever tricks and more about routine. Keep everything updated, use fewer and better plugins, protect every login, keep backups you can restore and watch your site so you notice problems early. A firewall closes the gap for vulnerabilities that do not have a fix yet. Work through the checklist above once, then make the routine part automatic.

Make the routine part automatic.A full backup before every update, updates in the right order, a visual check of every page, uptime and SSL monitoring and a clear monthly report. Try WP Beekeeper free for 14 days, no credit card needed.

Start free trial →