Why WordPress Sites Get Targeted
WordPress powers a huge share of the web, which makes it a common target for automated attacks — not because it's inherently insecure, but because outdated plugins, weak passwords, and unpatched core files are everywhere at scale.
Most attacks aren't a person manually targeting your site. They're bots scanning thousands of sites for the same handful of known weaknesses.
- ✓Keeping WordPress core, themes, and plugins updated closes the majority of known vulnerabilities.
- ✓Backups don't prevent an attack, but they're what actually lets you recover from one.
- ✓Security and backups work together — one reduces risk, the other limits the damage.
Where Sites Actually Get Compromised
Most WordPress security incidents trace back to one of a small number of entry points.
Weak passwords and no rate limiting make brute-force login attempts easy.
Unpatched plugins are the single most common way sites get breached.
Overly permissive file access lets malicious scripts write to your server.
Not a way in, but the reason a successful attack can become permanent data loss.
A Backup Strategy That Actually Holds Up
A single backup sitting on the same server as your live site isn't really a backup — if the server goes down, so does the copy. The 3-2-1 rule fixes that.
// The 3-2-1 backup rule 3 copies // the live site plus two backups 2 formats // e.g. server storage and cloud storage 1 offsite // at least one copy stored away from the server
A Basic Hardening Checklist
Why Automation Matters Here
Where Beginners Go Wrong
Breaking Down What You Just Learned
Most attacks are automatedBots scan for known, unpatched weaknesses rather than targeting you personally.
Updates close the biggest gapsOutdated plugins are the most common way sites get breached.
3-2-1 makes backups reliableThree copies, two formats, one offsite.
Automate what you can't rememberScheduled backups don't depend on anyone remembering to run them.
Test your restoresAn untested backup is only a hope, not a guarantee.
Try It Yourself
Install a backup plugin, run one manual backup, then actually restore it to a staging copy of your site to confirm it works before you need it for real.
Harden and Back Up Your Capstone Site
Getting your site ready to survive a bad day
By the end of today, your capstone site should be updated, hardened, and backed up on a schedule you don't have to think about.
- Update WordPress core, your theme, and every plugin.
- Enable two-factor authentication on your Administrator account.
- Install a security plugin and enable its login protection.
- Set up automated backups with at least one offsite storage location.
- Restore a backup to a staging site to confirm it actually works.
Recap
The single biggest thing that keeps known vulnerabilities closed.
Three copies, two formats, one stored offsite.
A second layer of protection for every Administrator login.
A backup only counts once you've confirmed it actually restores.
Key Takeaways
- Most WordPress attacks are automated bots exploiting known, unpatched weaknesses.
- Keeping core, themes, and plugins updated closes the majority of those weaknesses.
- Follow the 3-2-1 rule: three copies of your data, two formats, one stored offsite.
- Automate backups on a schedule rather than relying on remembering to run them manually.
- Always test a restore — an unverified backup isn't a real safety net.