Last updated: · By Ryan Walsh
WordPress security basics are a short set of habits that reduce your exposure to the attacks most sites face: keep WordPress, your plugins, and your themes updated; use strong, unique passwords with multifactor authentication; back up your site; and watch for suspicious activity. The official WordPress hardening guide notes that many attacks are carried out automatically by malicious software bots, so these defaults matter even on a small site that seems unlikely to be targeted.
This guide explains each basic in plain language, what it protects against, and how to put it into practice. Use it as a checklist for a new site or as an audit for an existing one.
Key Takeaways
- Updates come first: The official WordPress security guide calls keeping WordPress, plugins, and themes up to date the most important step for WordPress security.
- Length and uniqueness matter: CISA defines a strong password as at least 16 characters, random, and unique to one account.
- Passwords alone are not enough: CISA says a strong password should be paired with multifactor authentication, which still protects an account if the password is stolen.
- Backups are your recovery plan: Back up your files and database on a schedule, store copies off your web server, and test restores.
- Fewer tools means fewer risks: Every unused plugin or theme is extra code that can contain flaws and needs updates.
What Are the Most Common Threats to WordPress Sites?
The most common threats are automated login attacks, exploits of outdated software, SQL injection, phishing, and malware. Each one targets a different weak point: your login page, your code, your database, or the people who manage the site.
- Brute force attacks use automated tools to try large numbers of username and password combinations until one works.
- Exploits of outdated software take advantage of known flaws in old versions of WordPress, plugins, or themes.
- SQL injection inserts malicious database commands through poorly protected input fields, which can expose or alter your data.
- Phishing uses fake emails or login pages to trick people into handing over credentials, which attackers can then reuse.
- Malware is malicious code that can deface pages, steal visitor data, or send spam, and it often gets in through one of the routes above.
Why Should You Keep WordPress, Plugins, and Themes Updated?
You should install updates for WordPress core, plugins, and themes as soon as they are released. The official WordPress security guide says keeping WordPress and all installed plugins and themes up to date is the most important step you can take. Updates close known security holes before attackers can use them.

Updates also fix bugs and improve compatibility, which reduces conflicts between plugins and themes. Each outdated plugin is a potential entry point, so a site with twelve plugins has twelve components to keep current. Check for updates at least weekly, read release notes for security fixes, and test major updates on a staging copy when you can. For a routine you can repeat, see a 15-minute weekly WordPress maintenance routine.
How Do You Create Strong Passwords for WordPress?
A strong password is at least 16 characters, random, and unique to one account, according to the U.S. Cybersecurity and Infrastructure Security Agency (CISA) in its guidance on requiring strong passwords. A password manager, which is an app that stores and fills in your credentials in encrypted form, makes that practical because you never have to memorize them.

Apply the same standard to every account that can log in, including editors, authors, and your hosting and FTP accounts. Avoid birthdays, pet names, and dictionary words, and never reuse a password from another site, because a breach somewhere else can expose it on yours.
- Generate each password with a password manager instead of creating it by hand.
- Give every person their own login rather than sharing one account.
- Change the password right away if a service you use reports a breach.
Should You Use Two-Factor Authentication on WordPress?
Yes. Two-factor authentication (2FA) asks for a second proof of identity, such as a time-based code from an app, after your password. CISA explains in its guide to multifactor authentication that a strong password alone is not enough, because MFA still protects your account if an attacker has already obtained the password.
Authenticator apps are a practical choice for most beginners, and many WordPress 2FA plugins support them. Use this setup process:
- Install a 2FA plugin from the WordPress.org plugin directory, after checking its update history and user reviews.
- Enable 2FA on your administrator account first, then on every editor and author account.
- Scan the setup QR code with an authenticator app and save the recovery codes in your password manager.
- Test a login in a private browser window before you log out of your current session.
How Can You Limit Who Can Access Your Site?
Limit access by giving each user the lowest role that lets them do their job. Only administrators should install plugins, change themes, and manage other accounts. Remove accounts for former staff and contributors promptly, since unused accounts are easy to overlook.
Review your user list every few months and check the role assigned to each account. For role definitions and step-by-step changes, read our guide to managing WordPress user roles and permissions.
How Do You Reduce Risk From Plugins and Themes?
Install only the plugins and themes you need, download them from trusted sources, and delete the ones you do not use. Every extra plugin adds code that may contain flaws and must be kept updated. Before installing one, confirm that it is actively maintained, shows a recent update date, and supports your WordPress version.
- Remove inactive plugins instead of leaving them installed.
- Delete unused themes, but keep one default theme as a fallback.
- Choose one security plugin for firewall rules, malware scanning, and login monitoring, rather than running several overlapping tools that can conflict.
- Test plugin updates on a staging site when your setup allows it.
Does Your Hosting and HTTPS Setup Matter?
Yes. Your host controls the server environment, and HTTPS protects the data that passes between your visitors and your site. HTTPS is the encrypted version of HTTP, and it relies on an SSL/TLS certificate to encrypt that traffic.
Choose a host that offers server-level firewalls, malware scanning, automated backups, and an easy way to install a certificate, and make sure every page loads over HTTPS. For setup steps, see how to enable HTTPS on WordPress with a free SSL certificate.
How Often Should You Back Up WordPress?
Back up your site at least as often as you change it: daily for sites with frequent updates or orders, and weekly for sites that change occasionally. A complete backup includes both your files and your database, and it should be stored somewhere other than your web server.
Test a restore at least once a year, because a backup you have never restored may fail when you need it most. Backup plugins can automate the schedule; compare options in the ultimate guide to WordPress backup plugins.
How Do You Monitor Your Site for Suspicious Activity?
Monitor login activity, file changes, and traffic so you notice problems early. Many security plugins and hosts can log failed logins and alert you when a new administrator account is created or core files change.
Watch for unknown administrator accounts, plugins you did not install, sudden traffic spikes, unexpected redirects, and pages or posts you did not publish. Checking these signs weekly takes only a few minutes and catches many problems early.
What Should You Do If Your Site Is Compromised?
If you suspect a breach, act quickly: isolate the site, restore a clean backup, and secure the accounts that could have been used to get in. Work through these steps in order.
- Put the site into maintenance mode or take it offline to limit further damage.
- Change the passwords for all admin, editor, hosting, and FTP accounts.
- Restore the most recent backup made before the problem started, then update WordPress, plugins, and themes.
- Remove unknown users, unfamiliar plugins, and any files you did not add, then run a malware scan.
- Enable 2FA and review your security settings before reopening the site.
For a more detailed walkthrough, read what to do if your WordPress site gets hacked.
WordPress Security Checklist at a Glance
Use this table to decide how often to perform each core task. The frequencies are practical starting points, and you should increase them for busier sites.
| Security task | What it protects against | Suggested frequency |
|---|---|---|
| Update WordPress, plugins, and themes | Known vulnerabilities in outdated software | Check weekly and install security updates promptly |
| Use unique 16+ character passwords | Brute force attacks and credential reuse | When creating accounts and after any reported breach |
| Enable two-factor authentication | Logins using a stolen password | Once per account, then review yearly |
| Review user roles | Excess permissions and forgotten accounts | Every few months |
| Back up files and database | Data loss from attacks or errors | Daily or weekly, matching how often you change the site |
| Monitor logins and file changes | Intrusions that go unnoticed | Weekly review, with alerts turned on |
| Keep HTTPS active | Interception of data sent between visitors and your site | Continuously; check certificate expiry dates |
Frequently Asked Questions
Is WordPress secure enough out of the box?
WordPress is a widely used platform, but how secure your site is depends on how you run it. Default installs still need updates, strong logins, and a reliable host. Applying the basics in this guide addresses the attack paths that matter most for beginners.
How do I know if my WordPress site has been hacked?
Common signs include unknown administrator accounts, unfamiliar files, redirects to other sites, sudden traffic changes, and search engine warnings. If you see any of these, change your passwords and follow a recovery process before doing anything else. Check your host and security plugin logs for clues about when the problem began.
Do I need a security plugin if my host has a firewall?
A host firewall is valuable, but it may not cover malware scanning, file change alerts, or login monitoring inside WordPress. A single security plugin can fill those gaps. Choose one tool rather than several, and test it before relying on it.
How often should I update WordPress?
Install security updates as soon as they are released, and check for other updates at least weekly. Waiting weeks leaves known flaws open for longer. Test major changes on a staging copy when possible, and keep a recent backup before updating.
Is two-factor authentication necessary for WordPress?
WordPress does not require 2FA by default, but CISA recommends pairing strong passwords with multifactor authentication. It is especially valuable for administrator accounts, because those accounts control the whole site. Enabling it takes only a few minutes per account.
Can I secure my WordPress site for free?
Many basics cost nothing: updating software, using unique passwords, enabling 2FA, and reviewing user roles. Some hosts include free SSL certificates, and several plugins offer free tiers for backups and scanning. Paid tools can add convenience, but they are not required to follow the essentials.
Conclusion
WordPress security basics come down to consistent habits: update everything promptly, use strong unique passwords with 2FA, limit user access, back up on a schedule, and monitor for trouble. Start with the checklist above and complete one item per day until your site is covered.
More on WordPress security basics
Related guides: What to Do If Your WordPress Site Gets Hacked · How to Enable HTTPS on WordPress With a Free SSL Certificate · How to Manage WordPress User Roles and Permissions
Free tools: How Much Does a WordPress Site Cost? Free Calculator
