Website & Development
WordPress Security: 12 Measures Against Hacks (B2B Checklist)
Copy for AI
WordPress security comes down to a few basics, done every single week.
Keep everything up to date, use strong logins with two-factor authentication, add a firewall and set the right user permissions.
The verdict: you don’t need expensive tools to secure WordPress. You need boring hygiene, kept up consistently.
WordPress powers roughly 40% of all websites. That popularity makes it a favourite target for automated attacks.
Below: 12 concrete measures to harden a business WordPress site (not a webshop), grouped from logins to infrastructure. A checklist at the bottom lets you tick them off.
Why is WordPress attacked so often?
Not because WordPress is insecure, but because it’s everywhere.
W3Techs measured it on 39.6% of all websites (and 58.4% of sites with a known CMS) in October 2026.
It’s simply the biggest target.
This is the open source platform those numbers are about:
WordPress.org, October 2026. The same core runs on blogs, webshops and B2B sites alike.
Attackers work automatically
Bots scan the entire web for known vulnerabilities and weak logins.
They don’t pick you. They pick whatever answers.
Plugins and themes are the open doors
More important still is where those vulnerabilities sit.
Patchstack’s State of WordPress Security in 2026 counted 11,334 new vulnerabilities in 2025, 42% more than in 2024.
Here’s where they were found:
So the core is generally well maintained. But every plugin and every theme you add is another door that can be left open.
Attackers move fast
For heavily exploited vulnerabilities, Patchstack measured a weighted median of 5 hours to the first exploit.
About half of the high-impact ones were exploited within 24 hours. And 46% of vulnerabilities had no developer fix yet when they were disclosed.
What this means for a B2B site
You don’t need to be a security expert, but you do need your basic hygiene in order.
A hacked business site costs you remediation work. It also costs trust with exactly the visitors you want to convert into leads.
How to build that trust is covered in building trust on your B2B website.
How do you secure the logins?
With four measures, because the login page is the most attacked spot on your site.
That’s where you get the quickest wins.
1. Strong, unique passwords for every account
Use a password manager so nobody falls back on “CompanyName2025”.
Reused passwords are the number one cause of hijacked accounts.
2. Two-factor authentication (2FA) on all accounts
This is the single most important measure you can take.
Even if a password leaks, an attacker doesn’t get in without the second factor (a code on your phone).
Make it mandatory for every user with admin rights.
3. Limit the number of login attempts
By default you can try a password an unlimited number of times, which invites brute-force attacks.
A plugin or your firewall that blocks after a few failed attempts closes that door.
4. Least-privilege user roles
Give nobody more rights than they need.
For example, an editor who only writes blog posts doesn’t need an administrator account. The fewer admin accounts, the smaller the risk if one is compromised.
Extra step: consider moving or shielding the default login URL. It won’t stop a targeted attack, but it keeps the bulk of automated bots away.
How do you keep plugins and updates under control?
By updating on a fixed rhythm, because updating is your most important defence.
It’s not maintenance you get around to “some day”. Since most vulnerabilities sit in plugins and themes, updating literally closes known holes before a bot finds them.
5. Keep core, plugins and themes up to date
Set security updates for the core to automatic.
For plugins, a fixed weekly or fortnightly moment is often wiser than blindly auto-updating everything. You first test an update on a staging environment, so you don’t wake up to a broken site.
The update screen tells you what’s waiting:
A fixed WordPress maintenance routine makes this a habit instead of a chore.
6. Delete what you don’t use
Every deactivated but still installed plugin or unused theme remains a risk.
Remove them completely.
Less code on your server means less attack surface, and a faster site at the same time. Our piece on too many WordPress plugins shows how to trim the stack.
7. Only install from trusted sources
Use plugins from the official directory or from well-known makers, with recent updates and an active maintenance team.
Avoid “nulled” (illegally copied) premium plugins entirely. They’re a classic delivery channel for malware.
Rule of thumb: a site with fifteen half-maintained plugins is more vulnerable than a tightly built site with five good ones.
With a new website or redesign, a critical look at your plugin stack is a free security win. Our shortlist of WordPress plugins for B2B is a good starting point.
Which measures belong at server and infrastructure level?
The ones underneath WordPress itself: hosting, connection and file permissions.
This is where you prevent an attack that does get through from doing a lot of damage.
8. Put a Web Application Firewall (WAF) in front of it
A WAF filters malicious traffic before it reaches your site, such as known exploit attempts and brute-force bots.
This can be done through a security plugin. Often it’s more effective at network level, with your host or CDN.
9. Enforce HTTPS across the entire site
A valid SSL certificate encrypts traffic between visitor and server and protects submitted data.
It’s a baseline expectation for any business site by now.
Make sure everything redirects to https automatically.
10. Set file permissions and disable the file editor
With the right file permissions an attacker can’t overwrite files.
WordPress’s hardening guide suggests three settings:
- Directories: 755
- Files: 644
- wp-config.php: add
DISALLOW_FILE_EDIT
Switching off the code editor in the dashboard stops anyone who does get in from injecting malicious code straight away.
11. Choose hosting with security built in
Good (managed) WordPress hosting adds server security, isolation between sites, automatic updates and malware scans.
That saves a lot of manual work and covers a layer you can’t reach with plugins alone. Compare the options in choosing web hosting and managed vs self-hosting.
How do you make sure you recover quickly after an incident?
With backups and monitoring, because no security is a hundred percent watertight.
So the question isn’t only whether you stop an attack, but how quickly you recover. Two measures make the difference between an annoying hour and a week of downtime.
12a. Automatic, offsite backups
Make a daily or weekly backup and store it separately from your server.
A backup sitting on the same hacked server is just as lost in an attack.
Test now and then whether you can actually restore one.
Our guide to website backups covers the rhythm and the restore test.
12b. Monitoring and malware scanning
Have a tool scan your site for suspicious files and unusual changes. It should send an alert as soon as something deviates.
The sooner you spot a breach, the less damage.
Many hacks go unnoticed for a long time.
Already hacked? Then follow the steps in WordPress hacked: what to do before you change anything else.
This safety-net layer also keeps disruption short during technical changes, such as a website migration without losing rankings.
The 12-point WordPress security checklist
Work through this list from top to bottom. The first points deliver the most security per minute of work.
- Keep core, plugins and themes up to date and switch on automatic security updates for the core.
- Remove unused plugins and themes completely, don’t just deactivate them.
- Only install plugins from trusted sources and avoid illegally copied premium plugins.
- Use strong, unique passwords with a password manager.
- Enable two-factor authentication for every account with admin rights.
- Limit the number of login attempts to stop brute-force attacks.
- Apply least privilege: give every user only the role they need.
- Shield your login page or move the default login URL.
- Put a Web Application Firewall in front of your site, preferably at network level.
- Enforce HTTPS across the entire site with a valid SSL certificate.
- Set file permissions correctly and disable the built-in file editor.
- Arrange automatic offsite backups and monitoring, and test your restore.
Short on time? Then this table shows where each measure lives:
| Layer | Measures | Who usually owns it |
|---|---|---|
| Logins | 4, 5, 6, 7, 8 | Site admin |
| Plugins and updates | 1, 2, 3 | Site admin or maintenance partner |
| Server and infrastructure | 9, 10, 11 | Host or developer |
| Recovery | 12 | Host, developer or maintenance partner |
Want to place this within a broader picture? Read the overarching guide to B2B website development.
A fast, clean site also performs better, so this approach ties in with your WordPress SEO. Check the speed side with our website speed test.
Is WordPress still the right choice?
Often, yes. It depends on the company.
Our experience: AI and digital-native companies are moving to agentic websites. They get no plugin updates, no security warnings and fast changes.
If that fits you, look at AI website development. If WordPress stays, read when to use WordPress first.
The short summary
Securing WordPress isn’t a matter of one magic plugin. It’s consistently sticking to a handful of basics.
Keep everything up to date and limit your plugin stack to what you use. Set up strong logins with two-factor authentication, put a firewall in front and arrange backups.
Most attacks are automated and go for the low-hanging fruit. With the basics in order, you fall outside the reach of the bulk of the bots.
We build B2B sites that convert and also stay maintainable and secure. Prefer to hand off the upkeep? Our website maintenance services cover updates, backups and monitoring.
Free website scan
Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.
We only use your details for your scan. No spam, unsubscribe anytime.