# WordPress Security: 7 Essential Checks for a Safer Site

Source: https://hostreta.com/2026/10/wordpress-security-checklist/

In this guide: A practical WordPress security checklist covering maintenance, accounts, protective controls, tested backups and incident readiness.

WordPress security depends on maintained software, protected accounts, appropriate hosting controls, and a workable recovery process. Vulnerabilities, stolen credentials, unsafe software and misconfiguration can all contribute to a compromise. No single plugin or setting removes every risk.

Use this checklist to lock down your site.

Table of Contents

[Toggle](#)

- [Why WordPress sites get hacked](#Why_WordPress_sites_get_hacked)
- [WordPress security updates and software hygiene](#WordPress_security_updates_and_software_hygiene)
- [WordPress security for logins and user access](#WordPress_security_for_logins_and_user_access)
- [WordPress security plugins and firewalls](#WordPress_security_plugins_and_firewalls)
- [Backups in your WordPress security plan](#Backups_in_your_WordPress_security_plan)
- [Regular WordPress security review](#Regular_WordPress_security_review)
- [Tools and hosting that help](#Tools_and_hosting_that_help)
- [Key Takeaways: WordPress Security](#Key_Takeaways_WordPress_Security)
- [A 7-step WordPress security plan for a small business](#A_7-step_WordPress_security_plan_for_a_small_business)
- [1. Record the assets that WordPress security depends on](#1_Record_the_assets_that_WordPress_security_depends_on)
- [2. Make WordPress security updates a controlled process](#2_Make_WordPress_security_updates_a_controlled_process)
- [3. Review accounts and practical recovery](#3_Review_accounts_and_practical_recovery)
- [4. Reduce unnecessary software and integrations](#4_Reduce_unnecessary_software_and_integrations)
- [5. Configure protective controls without breaking the site](#5_Configure_protective_controls_without_breaking_the_site)
- [6. Prove that backups can restore the business](#6_Prove_that_backups_can_restore_the_business)
- [7. Maintain monitoring and an incident owner](#7_Maintain_monitoring_and_an_incident_owner)

- [WordPress security checklist: evidence to record](#WordPress_security_checklist_evidence_to_record)
- [If you suspect a WordPress security incident](#If_you_suspect_a_WordPress_security_incident)
- [Common WordPress security mistakes](#Common_WordPress_security_mistakes)
- [A practical maintenance schedule](#A_practical_maintenance_schedule)
- [WordPress security questions from small business owners](#WordPress_security_questions_from_small_business_owners)
- [Which security plugin is best?](#Which_security_plugin_is_best)
- [Can I handle WordPress security myself?](#Can_I_handle_WordPress_security_myself)
- [Do file permissions have one correct setting?](#Do_file_permissions_have_one_correct_setting)
- [Does a backup service replace prevention?](#Does_a_backup_service_replace_prevention)

- [Official WordPress security references](#Official_WordPress_security_references)

## Why WordPress sites get hacked

WordPress’s popularity makes it a target for automated attacks that scan millions of sites for known weaknesses. Common entry points:

- Vulnerable plugins and themes that expose known weaknesses.

- Weak or stolen passwords and brute-force login attempts.

- Nulled (pirated) themes and plugins containing hidden malware.

- Outdated WordPress, PHP, or server software.

- Compromised hosting accounts or shared server neighbors.

- Excessive user permissions and forgotten accounts.

Attackers usually aren’t targeting you specifically. They want server resources, SEO spam links, redirects, or a place to host phishing pages.

## WordPress security updates and software hygiene

- ☐ Keep WordPress core updated. Minor security releases update automatically by default; apply major updates after testing.

- ☐ Update plugins and themes promptly, especially security releases. Enable auto-updates for trusted, simple plugins.

- ☐ Delete unused plugins and themes — deactivated code can still be exploited.

- ☐ Use only reputable sources: WordPress.org or trusted developers. Never use nulled software.

- ☐ Use a current PHP version supported with security updates.

- ☐ Test big updates on staging — see [How to Safely Update WordPress](https://hostreta.com/2026/10/wordpress-updates/).

- ☐ Remove old test sites and backups stored inside your public web folder.

- ☐ Set correct file permissions (typically 755 for folders, 644 for files) and protect wp-config.php.

## WordPress security for logins and user access

- ☐ Unique, strong passwords for every user, generated by a password manager.

- ☐ Two-factor authentication (2FA) for all administrators and editors — see [Strong Passwords & 2FA](https://hostreta.com/2026/09/strong-passwords-mfa/).

- ☐ Don’t use “admin” as a username.

- ☐ Limit login attempts or use rate limiting to block brute force.

- ☐ Consider changing the login URL to reduce bot noise — see [How to Change the WordPress Login URL](https://hostreta.com/2026/10/how-to-change-the-wordpress-login-url/).

- ☐ Use the least privilege principle: give users the lowest role they need — see [WordPress User Roles Explained](https://hostreta.com/2026/10/wordpress-user-roles/).

- ☐ Review users regularly and remove old accounts (former employees, freelancers).

- ☐ Review XML-RPC dependencies before changing access; connected applications and Jetpack features may require it.

- ☐ Consider passkeys where supported for phishing-resistant logins.

## WordPress security plugins and firewalls

- ☐ Install one reputable security plugin offering a firewall, malware scanning, and login protection — see [Best WordPress Security Plugins Compared](https://hostreta.com/2026/10/best-wordpress-security-plugins-compared/).

- ☐ Use a WAF at the hosting or CDN level (e.g., Cloudflare) for protection before traffic reaches WordPress.

- 
☐ Disable file editing in the dashboard by adding to wp-config.php:

  define( 'DISALLOW_FILE_EDIT', true );

- 
☐ Force HTTPS across the entire site.

- ☐ Add security headers (e.g., Strict-Transport-Security, X-Content-Type-Options, Referrer-Policy, and a well-tested Content Security Policy).

- ☐ Enable activity logging to track logins and changes.

- ☐ Set up uptime monitoring and Search Console security alerts.

## Backups in your WordPress security plan

- ☐ Automatic daily backups stored off-site, following the 3-2-1 rule.

- ☐ Test restores regularly.

- ☐ Keep a recovery checklist ready — who to contact, how to restore, what to change.

- ☐ Know the signs of a hack: unexpected redirects, spam pages in Google, new admin users, unknown files, warnings in browsers or Search Console.

- ☐ Bookmark [How to Fix a Hacked WordPress Site](https://hostreta.com/2026/10/how-to-fix-a-hacked-wordpress-site-step-by-step/).

## Regular WordPress security review

- Update core, plugins, and themes.

- Review users and remove unnecessary accounts.

- Run a malware scan.

- Confirm backups completed and test one restore quarterly.

- Check Search Console for security issues.

- Review security plugin alerts.

Further reading: [official WordPress documentation](https://wordpress.org/documentation/)

## Tools and hosting that help

A fast, well-supported host makes every WordPress task smoother. [Kawedma WordPress hosting](https://kawedma.com/wordpress-hosting.php) and [managed WordPress hosting powered by Rocket.net](https://my.hosting.com/aff/08a016e41d3100e5460ff6ebee1b5e0a91e643d6) include staging sites for safe testing, while [shared hosting from Hosting.com](https://my.hosting.com/aff/279b8376451ad79ddf8c565d9a897e29387ab1eb) or [Kawedma shared hosting](https://kawedma.com/shared-hosting.php) suit smaller sites. Protect the site with an [SSL certificate](https://kawedma.com/ssl-certificates.php) and automatic backups from [CodeGuard](https://kawedma.com/codeguard.php).

## Key Takeaways: WordPress Security

- Maintain software, protect accounts, and investigate unsafe or unsupported components.

- Update everything promptly and delete what you don’t use.

- Use 2FA, strong passwords, and least-privilege roles.

- Add a firewall, malware scanning, and security headers.

- Keep tested off-site backups and a recovery plan.

## A 7-step WordPress security plan for a small business

A useful WordPress security checklist gives each action an owner, a verification method, and a response when something fails. A list of installed plugins is not enough. Start by documenting what the website does, who administers it, where customer data is stored, and which external services can change the site. This inventory makes subsequent decisions more specific and easier to maintain.

The workflow below is for routine prevention and preparedness. If you already suspect an intrusion, use the incident section before making broad changes. Avoid deleting unknown files or replacing a live database while you are still trying to understand what happened. A recovery action can remove evidence or overwrite legitimate orders and enquiries if its scope is not clear.

### 1. Record the assets that WordPress security depends on

Record the services, account owners and recovery routes involved in operating the site.

List the production site, staging copies, hosting account, domain registrar, DNS provider, business email, backup storage, and administrative accounts. Include integrations that can publish content or deploy code. A WordPress security review that considers only the dashboard can overlook an exposed hosting account or a forgotten test site that still has access to sensitive information.

For each asset, record the owner and a safe recovery route. Store this information in an access-controlled place available to the people responsible for the website. Do not put credentials into a public document or ordinary website article. An inventory should help authorized people find the right account, not create another collection of unprotected passwords.

For example, a business may use an agency to build the website while retaining ownership of the domain and hosting. Document that division explicitly. The agency’s access should have a purpose and an expiry or review point. This is an operational example, not a claim that a particular division of responsibility is required for every organization.

### 2. Make WordPress security updates a controlled process

Record the current core, plugin, theme, and runtime versions. Compare update notices with the maintainers’ information and prioritize relevant security fixes. A maintenance routine should be frequent enough to handle urgent updates rather than waiting for a monthly calendar entry. On the other hand, pressing every available update button without a recovery plan can create an avoidable outage.

Before a significant change, confirm that you have a current backup and know how to restore it. Use a staging copy for compatibility checks where available. Test the functions that matter to the business: sign-in, navigation, forms, search, purchases, and email delivery. Keep the test focused on real workflows rather than checking only whether the homepage still loads.

Do not let staging become a permanent excuse for delaying a known security fix. If compatibility prevents an update, document the affected component and evaluate an alternative or a temporary reduction in exposure with qualified support. WordPress security maintenance needs both a way to apply changes and a way to resolve the cases where changes cannot be applied normally.

### 3. Review accounts and practical recovery

Give each person a named account and the minimum permissions their work requires. A writer who submits drafts normally does not need administrator privileges. Review old contractor accounts and integrations alongside staff access. Before changing or removing access, confirm who owns the account, whether it is still in use, and whether business content needs to be reassigned.

Use strong, unique credentials and a supported additional authentication method for privileged access. Keep recovery codes protected and verify the recovery process without deliberately locking out the only administrator. WordPress security improves when authentication is strong and recoverable. A setup that relies on one person’s unavailable phone can leave the business unable to maintain the site.

Protect the associated email account and domain account as well. Email often participates in password recovery, while DNS and hosting accounts can affect the website independently of WordPress. Evaluate these as connected parts of the same operating environment. Do not describe a changed login address as a substitute for authentication, timely updates, or appropriate permissions.

### 4. Reduce unnecessary software and integrations

List active and inactive themes and plugins, their purpose, and their maintainer. Review abandoned or unused components and plan their removal through a reversible maintenance process. Keep the theme needed for the site’s actual configuration and any justified fallback arrangement. Do not delete files solely because their names are unfamiliar; investigate their source and role first.

Install software from trusted distribution channels and confirm that updates are still available. A premium license affects access to support and updates; it is not proof that software cannot contain a vulnerability. Similarly, a free plugin is not automatically unsafe. WordPress security decisions should consider maintenance, permissions, compatibility, and documented behavior instead of price alone.

Review integrations before disabling shared interfaces such as XML-RPC or the REST API. A site may rely on them for publishing, applications, or connected services. Check the dependencies and apply an appropriate control to the actual exposure. Blocking an interface without understanding its use can break legitimate operations while leaving unrelated entry points untouched.

### 5. Configure protective controls without breaking the site

Verify controls against actual workflows rather than relying only on installed features.

Identify which layer provides login protection, malware alerts, and request filtering. A host, CDN, and WordPress plugin can all participate. Document their responsibilities so the team knows which dashboard to investigate. More products do not automatically mean stronger WordPress security, especially when overlapping rules create lockouts or make it hard to explain which control blocked a request.

Apply new firewall rules gradually and test important functions. A checkout callback, form submission, or administrative request may resemble traffic a generic rule tries to block. Keep a narrow, documented exception process instead of disabling the whole firewall when a false positive appears. Preserve evidence of the affected request without copying sensitive customer information into public support messages.

Use HTTPS consistently and investigate mixed-content or certificate problems. Advanced headers need testing and an understanding of the domains and embedded resources involved. For example, a restrictive content policy can break payment tools or embeds. HSTS has persistence and deployment implications, so establish reliable HTTPS coverage before choosing a broad policy.

### 6. Prove that backups can restore the business

Check the backup scope and perform an isolated restore test.

Check what the backup actually contains, where it is stored, how long versions are retained, and who can restore it. A database copy alone does not necessarily include uploaded media, plugins, or configuration. A full collection of files without the corresponding database may also be insufficient. WordPress security planning should identify the components needed for a working recovery.

Choose a backup frequency according to how much recent activity the business can afford to lose. A small brochure site and a busy store have different recovery needs. Daily backups are not automatically sufficient for a site receiving frequent orders. Keep copies separate from the production environment and consider whether the same compromised account could delete both the site and its backups.

Test restoration in an isolated environment. Confirm that the site loads and that representative functions work. Prevent a test copy from sending live customer messages or processing real payments. Record the restore date, the backup used, the person who performed it, and any missing pieces. A successful backup notification is useful evidence of a job; a tested restore is evidence of recoverability.

### 7. Maintain monitoring and an incident owner

Decide who receives security alerts and how urgent messages reach that person. Review alerts for unexplained administrators, unusual changes, malicious redirects, unexpected publishing, and repeated authentication failures. A scanner’s clean result does not prove that every part of a site is safe, but monitoring can help identify a reason to investigate before customers report a problem.

Keep records with an appropriate retention period and access control. Logs can contain IP addresses, identifiers, or request details, so avoid publishing them as ordinary article attachments. When asking for support, share the minimum relevant information through an appropriate channel. WordPress security monitoring should improve investigation without becoming another source of unnecessary data exposure.

Create a short escalation route naming the website owner, hosting support, technical maintainer, and any specialist incident help. Establish who can approve downtime and who communicates with customers. This is particularly valuable when a team spans time zones. Monitoring is only actionable when someone knows what to do with the alert.

## WordPress security checklist: evidence to record

Control
Evidence
Review trigger

Software maintenance
Component inventory and last verified update
A security notice or planned release

Administrative access
Named owner, purpose and permission level
Staff or supplier changes

Backups
Scope, retention and isolated restore result
New business workflow or failed job

Firewall and alerts
Responsible layer and tested contact route
New integration or false positive

Incident readiness
Contacts and recovery decision process
A rehearsal or actual incident

Use the table as a working record, not a public declaration that the site is perfectly secure. Mark unknown items as unknown and give them a follow-up owner. WordPress security benefits from honest gaps because they can be investigated. A completed-looking checklist with no supporting evidence can conceal exactly the dependency that matters during an outage.

## If you suspect a WordPress security incident

Document suspicious behavior and coordinate investigation with trusted support.

First record what you observed and when: the affected URL, warning message, unexpected account, or suspicious redirect. Use a trusted device and established support channels. Contact the hosting provider or maintainer and preserve relevant evidence. The [official WordPress hacked-site guidance](https://wordpress.org/documentation/article/faq-my-site-was-hacked/) is a useful reference for organizing the response.

Decide whether temporarily restricting the affected service is necessary to protect visitors. This decision should account for the site’s function and the evidence available. Do not simply hide a warning and continue taking customer information. If sensitive information might be involved, use appropriate professional advice about investigation and any obligations relevant to the business.

Plan recovery around a known clean state and the identified entry point. Restoring an older backup may remove visible damage while leaving the vulnerable component or compromised credential in place. Likewise, changing a password alone will not remove malicious files. Verify the relevant accounts, software, and integrations as part of the recovery plan rather than treating one cleanup action as a complete solution.

For stores and other frequently updated sites, consider legitimate activity since the last clean backup before overwriting data. An unplanned restore can lose orders or submissions. After recovery, retest important workflows and review monitoring. See our [hacked WordPress recovery guide](https://hostreta.com/2026/10/how-to-fix-a-hacked-wordpress-site-step-by-step/) for the broader workflow, and use specialist help when the scope is uncertain.

## Common WordPress security mistakes

- Confusing a hidden login page with strong authentication. It may reduce routine noise, but it does not replace access controls.

- Applying one permission command everywhere. Ownership and hosting configuration matter; investigate before changing permissions recursively.

- Stacking overlapping protection plugins. Assign responsibilities and test the resulting configuration.

- Keeping every backup inside the same public folder. Assess exposure and separate recovery copies from production access.

- Assuming a restored homepage means full recovery. Check the entry point, accounts, files, data and business functions.

- Ignoring alerts until a monthly review. Security notices and suspicious activity may need earlier action.

## A practical maintenance schedule

Use automated notifications for events that require prompt attention, review backup failures and relevant update notices regularly, and schedule deeper access and restore reviews. The exact frequency depends on site activity and available support. WordPress security work should reflect actual business risk and the time needed to recover, rather than a promise that every website can be secured in a fixed number of minutes.

After a major integration change, revisit the checklist. A new payment provider, booking system, or automation can introduce additional accounts and dependencies. Update the inventory and monitoring route at the same time as the feature launch. This keeps maintenance aligned with the site that exists today instead of the simpler site the business had last year.

## WordPress security questions from small business owners

### Which security plugin is best?

There is no universal winner for every hosting environment. Compare the protection you already receive, the specific features you need, support, resource use, and compatibility. Our [WordPress security plugin comparison](https://hostreta.com/2026/10/best-wordpress-security-plugins-compared/) can help structure the shortlist. Test the chosen configuration instead of treating installation as proof of protection.

### Can I handle WordPress security myself?

You can own routine inventory, account reviews, update checks, and backup verification if you understand the tools and have a recovery route. Escalate unexplained compromise, complex server changes, or uncertain data exposure to qualified support. Keeping a record of what you know and what remains uncertain helps both self-managed maintenance and professional assistance.

### Do file permissions have one correct setting?

No universal setting is safe for every deployment. The values often mentioned in tutorials are starting points that depend on ownership, the web server, and the host’s configuration. Follow your hosting guidance and the [official permissions documentation](https://developer.wordpress.org/advanced-administration/server/file-permissions/). Do not make files broadly writable to solve an unexplained update failure.

### Does a backup service replace prevention?

No. Backups support recovery, while maintenance, access control, and monitoring address other parts of WordPress security. Review the backup scope and test restoration. A service with frequent copies can still be unsuitable if its retention is too short or no one knows how to obtain a working restore when the dashboard is unavailable.

## Official WordPress security references

For maintained background, consult the [WordPress security handbook](https://developer.wordpress.org/advanced-administration/security/), its [hardening guidance](https://developer.wordpress.org/advanced-administration/security/hardening/), and the [backup documentation](https://developer.wordpress.org/advanced-administration/security/backup/). Use those references to check configuration decisions for your own environment. This article is a practical planning framework and does not represent a security audit of your site.
