Hacked WordPress Site? How to Recover Using Backups
A calm, ordered plan for recovering a hacked WordPress site: choosing the right backup, restoring it, and locking things down so the attacker can't walk straight back in.

Website security for small business does not come from a single plugin or a promise that your site “can’t be hacked”. It comes from layers: server isolation, malware scanning, a firewall, regular updates, long passwords with two-factor login, an encrypted connection, and backups that bring you back if everything else fails. Each layer covers a gap the others leave.
This guide covers what each layer does, who is responsible for it (you or your host), and what to check today. Nobody can honestly promise perfect protection, but the right layers make an attack much harder and recovery much faster.
Because most attacks are automated and do not pick victims by name. Bots scan thousands of sites for a plugin with a known vulnerability or a login page that accepts a weak password, then attack whatever they find.
The goal is usually your site itself: sending spam, hosting phishing pages, redirecting visitors to shady sites or planting hidden links. The result for your business is browser warnings, email landing in spam and customers who lose trust. “Too small to matter” is not a security plan.
Seven core layers. Some run on the server and belong to your hosting provider; others live inside your site and belong to you or whoever runs it:
| Layer | What it stops | Usually responsible |
|---|---|---|
| Account isolation | A problem on a neighbouring site spreading to yours | Host |
| Malware scanning | Infected files going unnoticed | Host, with you acting on alerts |
| Web application firewall (WAF) | Malicious requests reaching WordPress | Host, an external service or a plugin |
| Updates | Exploits of known holes in old plugins and themes | You or your site manager |
| Passwords and 2FA | Guessed or stolen passwords | You and every user on the site |
| SSL/HTTPS | Eavesdropping between visitor and server | Host issues the certificate; you make sure the site uses it |
| Backups | Losing the site when other layers fail | Host, plus your own copy |
Account isolation means each site on a shared server runs in its own space with set resources, so a compromised or overloaded account cannot reach another account’s files or eat the whole server.
Without good isolation, the weakest site on a shared server can become a back door to yours. You cannot see or control this layer, so ask about it before you buy.
Malware scanning checks your site’s files for known malicious code or suspicious behaviour, then alerts you or quarantines the infected file. Its main value is early detection, before Google or your customers notice.
A typical infection hides well, such as a tiny PHP file tucked among plugin files, so continuous server-level scanning beats a manual scan every few months. But scanning finds the problem; it does not close the hole it came through.
A web application firewall (WAF) is a filter that inspects every request to your site and blocks those matching known attack patterns, such as attempts to inject commands into your database (SQL injection) or scripts into your pages (XSS).
A WAF can run on the hosting server, as an external service your visitors pass through first (usually set up through DNS), or as a WordPress plugin, which only runs once the site starts loading and so uses some of its resources. Ask your host what it provides at server level before stacking another layer on top; duplicating the same layer can slow your site without adding protection. Also limit failed login attempts to stop brute-force bots that try thousands of passwords.
Because most break-ins exploit known, published vulnerabilities in plugins and themes that were never updated. Once a fix ships, the flaw is public, and sites that lag behind become easy targets.
A staging site is an exact copy of your site for testing updates. For a full routine, see our monthly WordPress maintenance checklist.
Length beats complexity. The US National Institute of Standards and Technology’s NIST SP 800-63B-4, published in July 2025, requires passwords of at least 15 characters when a password is the only login factor, and at least 8 characters when it is combined with another factor. The same guidance forbids forcing mixed character types and forbids requiring periodic password changes without evidence of compromise.
In practice:
Give each WordPress user the lowest role they need: a content writer needs Author or Editor, not Administrator. Remove accounts for former staff and temporary developers promptly, and never share one admin login.
No. An SSL certificate encrypts the connection between the visitor’s browser and the server, so nobody on the network can read passwords or form data in transit. It does nothing to stop someone exploiting an outdated plugin: the padlock means “encrypted connection”, not “hack-proof site”.
HTTPS is still essential, as browsers flag unencrypted pages. Check that the certificate covers your domain and www, that http redirects to https, and that renewal is automatic.
Because every other layer reduces risk without eliminating it. A backup brings your site back after a hack, an accidental deletion or a broken update.
A useful backup is:
Keep your own full copy before major changes too. If you do get hacked, follow our guide to recovering a hacked WordPress site from backups; restoring without closing the hole brings the problem back.
Start with the steps that block the most common attacks. None needs technical skills:
Your host is responsible for the server and the layers that run on it; you are responsible for plugins, updates, users and passwords inside WordPress. Many breaches happen when each side assumes the other has it covered.
Every Start Bigger hosting plan includes CloudLinux account isolation, malware scanning with Imunify360 and Monarx, free SSL for every domain and subdomain, and daily JetBackup backups stored separately from the hosting server, kept for up to 60 days depending on the plan, which you can restore yourself from cPanel (details in our backup policy). WP Toolkit also gives you a staging copy to test updates safely.
The WordPress layers stay with you on regular hosting. If you would rather not handle them yourself, our Managed Site service takes care of updates, backups and security for one WordPress site while you keep your WordPress dashboard access. For a detailed comparison, read hosting vs managed WordPress: how to choose.
No. A security plugin is a useful layer, especially for protecting the login page and scanning files, but it does not replace updates, long passwords and backups. Running several security plugins that do the same job can cause conflicts and slow the site without adding protection.
Changing it cuts down the noise from bots that target the default address, but on its own it is not real protection. What matters more is a long, unique password, two-factor authentication and a limit on failed login attempts.
Current NIST guidance advises against forced periodic changes, because they push people towards predictable patterns such as adding a number at the end. Change a password immediately if you suspect it leaked or when someone who knew it leaves, and always keep it long and unique.
Price alone does not decide security. What matters is what the host does at server level: account isolation, malware scanning, backups stored off the server and keeping server software patched. Ask about those points specifically before you buy.
Do not start deleting files at random. Change your passwords, contact your host's support and work out roughly when the infection began. Then restore a clean backup from before that date and close the hole the attacker used by updating or removing the affected plugin.
A calm, ordered plan for recovering a hacked WordPress site: choosing the right backup, restoring it, and locking things down so the attacker can't walk straight back in.
An honest look at what a server in Germany means for visitors in Jordan and the Gulf: what distance really adds, when it matters, how caching and a CDN reduce it, and how to measure it yourself.
A checklist for recording every online asset your business depends on, who controls it and when it renews, so a departing developer or employee never takes your domain or site with them.
We answer on WhatsApp Saturday to Thursday, 9:00 am – 9:00 pm Amman time (GMT+3)