Website Development

WordPress Security Hardening: A Complete Guide to Protecting Your Site

43% of the web runs on WordPress making it the largest target. Here is every practical hardening measure in order of impact.

Athar Ahmad
Reviewed by Athar AhmadFounder & CEO · Written by the SA Solutions team
Published March 21, 2026 Updated October 23, 2026 4 min read
On this page
  1. The WordPress security threat landscape
  2. Layer 1 – Updates and software hygiene
  3. Layer 2 – Authentication hardening
  4. Layer 3 – Server and file security
  5. Layer 4 – Security plugin and monitoring
  6. What to do if your WordPress site is hacked
  7. Need your WordPress site security hardened or post-hack cleaned?
  8. Frequently asked questions

43% of the web runs on WordPress making it the largest target. Here is every practical hardening measure in order of impact.

  • 43% — of the web runs on WordPress
  • 50-60% — of hacks exploit outdated plugins/themes
  • Layer 4 — hardening: updates, auth, server, monitoring
  • 24-48h — WordPress patches security vulnerabilities

WordPress powers 43% of the web, making it the largest attack surface of any CMS. Most successful attacks exploit outdated software, weak credentials, or misconfigured permissions – not sophisticated zero-day exploits. This guide covers every practical hardening measure, in order of impact.

The WordPress security threat landscape

Attack vector Percentage of compromises Primary prevention
Outdated plugins/themes 50-60% Automatic updates and plugin audits
Weak passwords / credential stuffing 20-30% Strong passwords plus 2FA plus login limits
Insecure hosting 10-15% Choose reputable managed WordPress hosting
Nulled plugins/themes 5-10% Never use pirated premium plugins or themes
Brute force attacks Constant Login attempt limits plus CAPTCHA plus 2FA
50-60% of hacks exploit outdated software

The single most impactful security action is keeping WordPress core, plugins, and themes updated. Most vulnerabilities are patched withwithin 24 hours of disclosure – but only if you apply the update.

Layer 1 – Updates and software hygiene

Enable automatic minor security updates

WordPress 5.5+ automatically applies minor security releases. Verify this is enabled: check wp-config.php for define('AUTOMATIC_UPDATER_DISABLED', true) – if present, remove it.

Update plugins and themes weekly

Go to Dashboard › Updates every week and apply all available updates. Apply major plugin version updates to staging first.

Delete deactivated plugins and unused themes

Deactivated plugins are still present in the file system and can be exploited. Delete, not just deactivate, everything you are not actively using.

Never use nulled (pirated) plugins or themes

Nulled plugins are the most common distribution vector for backdoors and malware. The free premium plugin always has a cost paid in your site’s security.

Layer 2 – Authentication hardening

Change the default admin username

The default ‘admin’ username is targeted by every automated brute force tool. Create a new administrator account with a non-obvious username, log in with it, then delete the ‘admin’ account.

Enforce strong passwords

Install Force Strong Passwords plugin. Use a password manager (Bitwarden, 1Password) to generate and store credentials.

Enable two-factor authentication

Install WP 2FA or Google Authenticator plugin. Require 2FA for all Administrator and Editor accounts. 2FA makes brute force attacks effectively impossible.

Limit login attempts

Install Limit Login Attempts Reloaded. Set maximum attempts to 5 per IP before a lockout.

Move the login page

Use WPS Hide Login to change the login URL from /wp-login.php to a custom path known only to your team. This eliminates the majority of automated login attacks.

Layer 3 – Server and file security

  • Protect wp-config.php: add rules to .htaccess to prevent direct HTTP access to your configuration file
  • Disable file editing in the dashboard: add define('DISALLOW_FILE_EDIT', true); to wp-config.php to remove the Theme and Plugin Editors
  • Set correct file permissions: files should be 644; directories 755; wp-config.php 600
  • Disable XML-RPC if unused: if you do not use the WordPress mobile app or any XML-RPC-dependent service, disable it via Wordfence or .htaccess

Layer 4 – Security plugin and monitoring

Wordfence Security

The most widely used WordPress security plugin. Includes a web application firewall, malware scanner, live traffic monitoring, and brute force protection.

Sucuri Security

Strong malware scanning, file integrity monitoring, and post-hack cleanup tools. Sucuri’s premium plan includes a CDN-based WAF that blocks attacks before they reach your server.

iThemes Security

Covers most hardening measures in one plugin: 2FA, login limits, file change detection, database backups, and security logging.

What to do if your WordPress site is hacked

Take the site offline immediately

If malware is actively serving spam or redirecting visitors, enable maintenance mode or contact your host to suspend the site.

Restore from a clean backup

If you have a backup from before the infection, restore it. This is by far the fastest remediation path.

Run a malware scan

Use Sucuri SiteCheck for a free external scan. Install Wordfence for a server-side file scan. Identify all infected files.

Reset all credentials

Change every password: WordPress admin accounts, FTP/SFTP, database, and hosting control panel.

Identify and close the entry point

Check server access logs to identify how the attacker got in. Update the vulnerable plugin or theme and apply all hardening measures above to prevent reinfection.

Need your WordPress site security hardened or post-hack cleaned?

Simple Automation Solutions performs WordPress security audits, hardening, and post-compromise recovery for businesses worldwide.

Book a Free Call
View Our Work →

Frequently asked questions

Is WordPress inherently insecure? +

No. WordPress core is actively maintained by a security team that patches vulnerabilities quickly, typically withwithin 24 hours of disclosure. The security issues that affect most sites are caused by outdated third-party plugins and themes, weak passwords, and misconfigured servers – not WordPress core itself.

Should I use a security plugin if my host already provides security? +

Yes. Managed WordPress hosts provide server-level security but cannot monitor WordPress application-level threats: a compromised admin account, a malicious plugin, or a PHP file uploaded through a vulnerability. A security plugin like Wordfence provides application-level monitoring that complements hosting-level security.

How often should I run a WordPress malware scan? +

Weekly automated scans are the minimum. Configure Wordfence or Sucuri to email you weekly scan results. Run an additional manual scan after installing a new plugin from an unfamiliar source, after a security incident on your hosting account, or whenever your site behaves unexpectedly.

Athar Ahmad
Athar AhmadFounder & CEO, SA Solutions · Certified Bubble.io Developer

Athar has spent more than 8 years building digital products and leads every SA Solutions project, from Bubble.io apps to AI automation for small and growing businesses. Read our editorial standards.

Other posts

Need help with your website or app?

Book a free 30-minute call and get honest advice and a clear next step.

Book a free callSee our services