November 1, 2026
WordPress security checklist for Zimbabwean business websites (2026 edition)
WordPress powers a huge share of business sites — and its popularity makes it a target. The 12-point checklist we run on every WordPress site we audit, ordered by risk.
Share this article
The short answer: WordPress is secure by default — insecure by practice. The vast majority of compromised WordPress sites we encounter trace back to a small, predictable set of mistakes: outdated plugins, weak admin credentials, un-monitored updates, and no backup rehearsal. This checklist covers the twelve items we check on every WordPress security review, ordered by how often each one turns out to be the actual hole. Work through it top-down; the first five items close most of the realistic risk.
The 12-point checklist
1. Update discipline (>60% of real-world incidents live here)
Outdated plugins — not WordPress core — are the standing classic. Old plugins with known vulnerabilities are the front gate for automated attacks that scan every WordPress site on the internet, continuously. Fix: update plugins and themes on a fixed rhythm (weekly at minimum for any site you earn from), remove plugins you don't use rather than leaving them dormant, and prefer plugins with active update histories.
2. Credential strength and uniqueness
Admin accounts with guessable passwords and the default "admin" username make the brute-force script's job trivial. Fix: unique strong passwords stored in a password manager, no shared accounts, and every human with admin duties having their own named account (so actions are attributable and revocable).
3. Backup you can actually restore
A backup that has never been tested is a hope, not a backup. Fix: automated off-server backups on a schedule, and do one real restoration drill — onto a throwaway location — so you know how recovery works before you need it under pressure.
4. Limit login attempts / protect the login page
Automated bots hammer WordPress login pages all day. Fix: rate-limit or lockout after several failed attempts, and disable or filter XML-RPC unless a specific tool needs it — this closes the noisiest automated attack surface a stock WordPress site waves at the internet.
5. Two-factor authentication for admins
A password alone — no matter how strong — is one phishing link away from being worthless. Fix: 2FA on every admin login. It's the cheapest control in this list relative to the damage it prevents.
Notice the pattern of the first five items: none of them cost money. Most WordPress risk closes through discipline, not spend.
6. HTTPS everywhere
For a business site in 2026 there's no decision here: browsers mark non-HTTPS sites as insecure, forms submitted without encryption are eavesdroppable, and payment-adjacent pages are non-starters without it. Fix: certificate installed, renewed automatically, and every page forced onto the secure connection.
7. Fewer admins
Every admin account multiplies your exposure to one stolen session. Fix: minimum privilege — editors edit, shop managers manage, and administrative rights get issued, reviewed, and revoked deliberately. Ex-staff and agency logins should be removed, not deferred.
8. File integrity and change control
Unknown files in your uploads folder or core files with a modification date you can't explain are how long-lived compromises stay invisible. Fix: periodic file-integrity checks (security plugins do a decent baseline), and any change to production goes through a person who knows why.
9. Hosting environment
Your site inherits its neighbourhood: hosting with server-level firewalls, malware scanning, and current PHP versions buys you defence you can't build yourself. Fix: confirm your hosting plan's security inclusions in writing (our hosting costs guide lists what to look for), and don't beggar the security line to save on the hosting line.
10. Monitoring and alerting
Compromise detected in a week is an incident; the same compromise detected in a year is a ruin. Fix: alerts on file changes and failed-login spikes, uptime monitoring with a human who responds, and a defined "who does what if the site's flagged" step — our compliance guide explains why that last point is also becoming a legal matter for personal-data holders.
11. Database hygiene
Old posts revisions, plugin leftovers, and unrotated accounts add clutter that's both performance debt and attack surface. Fix: scheduled cleanup and removing data you no longer use — the same maintenance our slow-site guide recommends for speed also reduces exposure.
12. A tested incident procedure
When something looks wrong, no one should be improvising. Fix: know how you'd snapshot the site, wipe, restore, and reset credentials — written down — including who to call. A compromise handled in an afternoon with evidence rarely becomes a business crisis.
Where professional testing earns its fee
This checklist removes common-band risks. For sites that matter — payment flows, member data, large audiences — a check from the outside in (what an attacker actually sees and can do) finds what self-inspection misses. That's our penetration testing service: same checklist discipline, adversarial evidence, plain-English report. Or start with the broader IT audit if your stack is more than WordPress alone. Send us your site URL and we'll scope which level fits.
Frequently asked questions
Is WordPress really less secure than other platforms?
It's differently targeted, not weaker. Because so many sites run specific popular plugins, attackers automate against those plugins' known weaknesses. A maintained WordPress site with current plugins is harder to compromise than an abandoned "alternative platform" site no one has patched in a year.
Do I need a paid security plugin?
The first five items on this list cost nothing but discipline and close most realistic risk. Paid security plugins add convenience — scheduling, file-integrity monitoring, firewall rules — and are worth it for earning sites, provided someone still does the human discipline the plugin can't.
How often should I update my WordPress plugins?
For a business site: on a fixed weekly rhythm, not when you remember. Revenue-relevant sites with e-commerce or membership features should check more often, and updates ideally go through someone who knows how to roll one back safely.
My site got hacked but I cleaned it. Why does it keep happening?
Because cleanup removed the evidence of entry, not the entry. Persistent compromises usually mean a backdoor file survives, a stolen credential is still valid, or the vulnerable plugin is still there. After any incident: fresh restore, full credential rotation, root-cause found, then retest.
