WebWorld.nl
Security

WordPress security audit: what should you check?

A practical technical check of weak spots, recoverability and configuration.

A WordPress security audit is more than checking whether plugins are up to date. A good audit looks at the whole chain: WordPress itself, accounts, plugins and themes, hosting, DNS, backups and the way changes are made.

1. Start with recoverability

The first question is not only “can this site be hacked?”, but also “how fast can we recover?”. So check whether backups are stored externally, made automatically and can actually be restored periodically. A backup on the same server is not a complete recovery strategy in a serious incident.

2. Take stock of software and access

Remove unused plugins, themes and accounts. Check administrator rights, enforce strong unique passwords and use two-factor authentication where possible. Also review SFTP, database and hosting accounts; WordPress is only one access point.

3. Check updates and vulnerabilities

Updates should happen on time, but not blindly on production. For business sites a staging process is wiser: test first, then go live in a controlled way. That combines security with continuity.

4. Look at server and application security

Check the PHP version, file permissions, HTTPS, security headers, brute-force protection, firewall rules and malware monitoring. Also look out for unexpected admin accounts, modified core files and unknown cron jobs.

5. Make security a process

An audit is a baseline. Without monitoring, maintenance and a recovery plan, that snapshot quickly goes out of date. For websites that matter for leads or revenue, security therefore belongs in day-to-day management.

How often should you audit?

A full security audit makes sense at the start of management and then at least once a year. Add an extra one after major changes, such as a new theme, a new integration or a migration to another server. Daily checks, such as updates and malware scans, belong to regular maintenance.

Free tools to get started

  • The Site Health page in WordPress (Tools → Site Health) for outdated software and settings
  • A security plugin for a malware scan and a check of the core files
  • Google Search Console for notifications about security issues
  • An overview of all users with administrator rights

What do you do with the outcome?

An audit produces a list of risks. Start with what has the biggest impact and is easiest to fix: missing backups, outdated plugins and unnecessary administrators. Plan larger changes, such as a PHP upgrade, and test them on staging first.

Frequently asked questions

Can I do an audit myself?

The basics, yes: checking updates, users and backups. Checking the server, the files and the code requires technical knowledge.

What does a security audit at WebWorld cost?

We like to start with a free technical website audit. In it we also look at security, updates and backups.

What if the audit finds malware?

Then acting fast matters. Our WordPress emergency help cleans the website, closes the gap and restores from a backup where needed.

Want to know where your website is at risk?

WebWorld combines hosting, security, monitoring and maintenance in one managed service.

View managed WordPress security →

Rather not manage this yourself?

We combine managed hosting, WordPress maintenance and support in one service.

Plan a free audit
WhatsApp WhatsApp