WordPress security audit checklist for non-developers

Practical WordPress security checklist for non-developers: plugin review, backups, user hygiene, file permissions and incident readiness.

WordPress security audit checklist for non-developers
Image by geralt from Pixabay

Most WordPress site managers are not developers, yet they are responsible for security decisions that affect business continuity and visitor trust. This checklist is designed for site owners, editors and small teams who need clear, actionable steps to audit a WordPress site, reduce common risks and prepare for incidents without writing code.

How to use this checklist

Work through sections in order. Mark items you complete and note anything you cannot do without developer access — then plan how to get that help. Many items are preventive and quick; others require a simple change in hosting control panels or a plugin setting.

Backups, restore testing and update policy

Backups, restore testing and update policy
Image by TheOtherKev from Pixabay

Backup essentials

  • Ensure automated, off-site backups exist for both files and the database. Backups should not be stored only on the same server as the site.
  • Keep at least one recent copy that you can restore quickly. Label backups with the date and a short note describing the scope (files, database, full site).

Test your restore

  • Test the restore process on a staging or local environment before you need it. A backup that cannot be restored is not useful.
  • Test restore by restoring at least one backup to a staging location to confirm the process works.

Update policy

  • Decide who is responsible for updates and how often they are performed. Prioritise security updates for WordPress core, themes and plugins.
  • If automatic updates are enabled, confirm they cover minor and security releases; if not, have a schedule and rollback plan.

Plugin and theme inventory and risk review

Create an inventory

  1. List every active plugin and theme, including the vendor name and the purpose (contact form, SEO, caching, analytics).
  2. Note plugins that have not been updated recently or those you do not recognise; these are risk candidates.

Risk indicators to watch for

  • Abandoned plugins: no updates for an extended period, no active support channel or broken review threads.
  • Plugins with excessive permissions or extra admin menus that you did not expect.
  • Plugins installed for convenience that duplicate functionality—fewer plugins is usually safer.

Actionable plugin review steps

  • Remove unused plugins and themes completely (not just deactivate).
  • Replace risky plugins with well-maintained alternatives where possible.
  • For critical functionality, consider paid, actively supported plugins rather than obscure free options; assess support and update cadence.

User accounts, roles and password hygiene

Account inventory and pruning

  • Export a list of user accounts and check last-login dates where available. Remove or suspend accounts that are no longer needed.
  • Check that user roles are appropriate—WordPress default roles are Administrator, Editor, Author, Contributor and Subscriber.

Principle of least privilege

  • Grant the minimum role required to accomplish a task. Editors and Authors do not need Administrator access.
  • Use separate accounts for individuals; avoid shared credentials for administrative access.

Password and authentication

  • Require strong, unique passwords. If you don’t use a password manager yet, see our guide to start one: A Beginner’s Guide to Password Managers and Passkeys.
  • Enable multi-factor authentication (MFA) for accounts with elevated privileges and for any account that can modify code or install plugins.
  • For teams, standardise on an enterprise password manager or shared vault to handle access and emergency access procedures; for guidance see Secure enterprise password manager deployment for teams.

Basic server and file permission checks

Hosting control panel and access

  • Use secure protocols for file transfer and administration: SFTP or SSH rather than plain FTP.
  • Limit the number of IP addresses or accounts that have SSH/SFTP access where your host allows it.

File permissions and key files

  • Restrict file permissions so that wp-config.php is not world-readable; 600 or 640 for files and 755 for directories is a common baseline.
  • Keep backups and sensitive files outside the public webroot where possible, and avoid storing credentials in plain text on the server.
  • Disable in-dashboard file editing by adding define('DISALLOW_FILE_EDIT', true); to wp-config.php.

Monitoring, incident readiness and essential plugins

Monitoring basics

  • Enable logging for login attempts and administrative actions. Check logs regularly or configure alerts for suspicious activity.
  • Set up uptime monitoring so you are notified if the site goes down; this helps you detect incidents quickly.

Incident readiness checklist

  • Create a simple incident playbook: who to contact, where backups are stored, how to take the site offline if compromised, and how to restore from backup.
  • Store incident credentials and procedure notes securely and separately from the site itself.
  • Practice a restore and incident response run-through at least once so the team knows their role.

Essential plugin types (not product recommendations)

  • A reliable backup plugin or host-level backup offering.
  • A security plugin that offers hardening checks, login protection and basic malware scanning.
  • An activity log plugin to track administrative changes and user logins.
  • An uptime monitor or external service to alert you to outages.

Quick win checklist (do these first)

  • Create and verify an off-site backup.
  • Remove unused plugins and themes.
  • Enable MFA for all admin accounts.
  • Disable file editing in the dashboard by setting DISALLOW_FILE_EDIT.
  • Test a restore to a staging environment.

What to escalate to a developer or host

  • Signs of a compromise: unexplained admin accounts, backdoors, modified core files or persistent redirects.
  • Complex permission changes, server configuration (web server, PHP settings) and host-level firewall rules.
  • When plugin conflicts break the site after an update — isolation and debugging usually require technical access.

Closing: make this checklist part of your routine

Treat this audit as living documentation. Repeat the checklist on a schedule that fits your site’s traffic and complexity, and after any major change. If you can complete the quick-win items immediately, you will eliminate many common risks without needing a developer. For password best practice and team vaults, follow the linked guides to improve account hygiene and emergency access.

Next steps: run the Quick win checklist now, document what you change, and plan a restore test within your team.

Share this articleXinf

About this article

  • Published November 9, 2026 · Last reviewed November 12, 2026
  • Written for defensive and educational purposes. Only test techniques on systems you own or have permission to assess.
  • Spotted an error or have new information? Tell our team and we will review it.

Written by

Arun Petrov

Covers pragmatic risk assessment, prioritization methods, and security measurement.

More articles by this author →

Join the discussion

Your email is never published. Please be respectful, and never post passwords, personal data or working exploits.