WordPress Security Audit: A 12-Point Checklist

A WordPress security audit is an overview of the security measures of your website. Yet, by conducting a WordPress security audit, you will be able to recognize additional security measures that have to be applied to make certain that your website is fully protected and secure. Why is that important, find out in the new Inkyy article.

Bojan SandićLead UI/UX at Inkyy 6 min read
WordPress Security Audit - What is it & why do you need it - Inkyy Web Design & Development Studio

A WordPress security audit is a structured check of your site’s defences: software, users, settings, files and backups. It shows you what is weak before an attacker finds it.

This guide gives you a practical 12-point checklist you can follow in an afternoon, explains why each check matters and tells you what to do if you find something wrong.

What is a WordPress security audit?

An audit does not make your site safe by itself. It is a review. You go through the parts of the site an attacker could use, record what you find and fix the gaps. The result is a short list of actions, ordered by risk.

Security is about reducing risk, not removing it. The WordPress developer handbook says the same: you cannot make a system perfectly secure, but you can limit access, contain damage and prepare to recover. Most hacked WordPress sites are not beaten by clever attacks. They are compromised through an outdated plugin, a weak password or a forgotten account.

Why audit your site regularly

Sites change all the time. Plugins are added, staff come and go and hosting settings shift. A site that was secure last year may have an unpatched plugin, an unused admin account or a broken backup today.

If an attacker gets in, they can inject spam or ads, redirect your visitors, steal customer data or use your server to attack others. The cost of cleaning up, and the damage to trust, is far higher than the cost of an audit. As a guide, run a quick check every quarter and a full audit at least once a year. Do it more often for shops, membership sites and any site that handles personal data.

A 12-point WordPress security audit checklist

1. Back up and test a restore

Start here, because every other step is safer with a backup. Make a full copy of the files and database and store it away from the server. Then test it. Restore the backup to a staging site and check that pages, media and forms work. A backup you have never restored is only a hope.

2. Update WordPress, plugins and themes

Outdated software is the most common way in. The WordPress Security Team states that only the latest version of WordPress is officially supported, although it backports some fixes to older versions as a courtesy. Check the Updates screen and update core, plugins and themes. For minor releases and trusted plugins, turn on automatic updates. For large or complex sites, test updates on a staging copy first. See the WordPress guide to updating.

3. Remove what you do not use

Every plugin and theme is extra code that can contain a flaw. Delete inactive plugins and unused themes, not just deactivate them. Replace anything the developer has stopped maintaining. Install plugins and themes only from the WordPress.org directory or from trusted, known companies. Never use “nulled” copies of paid plugins.

4. Check your PHP and database versions

Old server software stops getting security fixes. WordPress.org currently recommends PHP 8.3 or greater, and MariaDB 10.11 or greater or MySQL 8.0 or greater. Check the versions in Tools, Site Health, and ask your host to upgrade if you are behind. See the WordPress requirements.

5. Review users and roles

Open the Users screen. Remove accounts you do not recognise, delete former staff and freelancers, and give each person the lowest role they need. Few people need Administrator. Avoid an account named “admin”, and use a personal account for each user, not shared logins.

6. Enforce strong passwords and two-factor authentication

Use a long, unique password for every account, kept in a password manager. Add two-factor authentication for all administrators and editors. The Two-Factor plugin from WordPress.org supports authenticator apps, backup codes and other methods. Even if a password leaks, a second factor can stop the login.

7. Limit login attempts

Bots try thousands of passwords against the login page. Add rate limiting or a login protection feature through your security plugin, your host or a firewall. Consider moving or restricting access to the login page if your host supports it.

8. Use HTTPS and sensible security headers

Your whole site should load over HTTPS, and HTTP should redirect to it. Check that the certificate renews automatically. Consider headers such as HSTS, X-Content-Type-Options and a content security policy, which your host or a plugin can add. Test the result with a free online header scanner.

9. Lock down files and the editor

Use sensible file permissions: 755 for folders and 644 for files, and 400 or 440 for wp-config.php. Add the line define( 'DISALLOW_FILE_EDIT', true ); to wp-config.php to turn off the built-in theme and plugin editor, because it gives an attacker who logs in a way to run code. These steps come from the Hardening WordPress handbook.

10. Scan for malware and known vulnerabilities

Run a malware scan with a reputable security plugin or your host’s scanner. If you use WP-CLI, the commands wp core verify-checksums and wp plugin verify-checksums --all compare your files with the official copies. Check your plugins and themes against a public vulnerability list such as the Patchstack database, and replace anything with an unpatched flaw.

11. Turn on logging and monitoring

You cannot react to what you cannot see. Use an activity log to record logins, user changes and plugin installs. Set up uptime monitoring and alerts. Add your site to Google Search Console and check the Security issues report from time to time.

12. Check your hosting and access

Your host is part of your security. Ask about server-level firewalls, isolation between accounts, malware scanning and backups. Use SFTP or SSH instead of plain FTP, and rotate keys and passwords when a developer leaves. See our post on IT security in the design process.

After the audit

  1. List what you found and rank each item as high, medium or low risk.
  2. Fix high-risk items first, such as outdated plugins, weak admin passwords and missing backups.
  3. Record the date and changes so you can compare next time.
  4. Schedule the next check. Put a quarterly reminder in the calendar.

What to do if you find a problem

If you suspect a hack, act calmly. Put the site in maintenance mode, change all passwords, including hosting, database and FTP, and restore from a clean backup made before the problem began. Update everything, scan again and contact your host, who can often help. Then find out how the attacker got in, so it does not happen again. If customer data may have been exposed, check your legal duties to report it.

A secure site is also a better-built site. If you are planning changes, read our guide to the web design process. If your site is old and hard to maintain, see our reasons for redesigning your website. Our design and web development teams can also help.

Frequently asked questions

How often should I run a WordPress security audit?

Run a quick check every quarter and a full audit at least once a year. Check more often if you run a shop, take payments or store personal data, and always after a major change or incident.

Can I audit my WordPress site myself?

Yes. The checklist above covers the main points and does not need specialist tools. A developer or security specialist can go deeper, especially on custom code and server settings.

Do I need a security plugin?

A good security plugin helps with scanning, login protection and logging, but it is not a substitute for updates, backups and strong passwords. Your host may already provide some of these features, so check before installing more.

What is the most common way WordPress sites get hacked?

Outdated or vulnerable plugins and themes, weak or reused passwords and compromised accounts are the most common causes. Keeping software updated and using two-factor authentication prevents most of these problems.


Need a secure WordPress site for a client?

Inkyy is a white label design and development team for agencies. Our in-house developers build and maintain WordPress sites under your brand. See our design services or book a 15-minute call.

Written by

Bojan Sandić

Lead UI/UX at Inkyy

Bojan leads UI/UX at Inkyy and works with agencies on websites, product design and brand identity.

Meet the team