Guide / 22 November 2026
Hacked WordPress site: what to do, in order
If your company's WordPress site looks compromised, call your hosting company or IT provider first, then cut off the attacker's access, keep a copy as evidence and restore from a clean backup. If personal data may be affected, check your duty to notify the data protection authority within 72 hours.
The short answer: change passwords and keys, take a full copy of the site as it is, restore from a clean backup or clean the site, update everything, remove unknown users and plugins, and look for anything the attacker left behind. We do not do cleanup or incident response; once the site is clean, an audit shows how they got in and what else is exposed.
Signs that a site has been compromised
A hacked site does not always look different to its owner. Attackers often prefer to stay hidden. The most common signs:
- new spam pages, usually visible only in search results, not in the site's menu;
- visitors sent to other sites, sometimes only those on a phone or arriving from a search engine;
- admin users that nobody in the company created;
- browser or search engine warnings that the site is dangerous;
- the hosting company suspends the account or reports unusual traffic or spam sending;
- unknown files on the server, especially PHP files in the uploads folder;
- company emails suddenly landing in customers' spam folders.
The first steps, in order
If the attack seems to be ongoing, call your hosting company or IT provider first. They have access to the server and its logs and can isolate the site. The steps below are the ones a technical team usually follows; use them as a checklist alongside them.
- Cut off the attacker's access. Change the passwords of every WordPress admin account, the hosting panel, FTP or SFTP, the database and the email linked to the site. Regenerate the secret keys in wp-config.php so that every open session is signed out. Change the API keys of connected services too, such as payment or delivery.
- Take a full copy as evidence. Before cleaning anything, copy the files, the database and the server logs as they are. Without that copy, nobody can later work out how the attackers got in or what they touched.
- Restore from a clean backup, or clean the site. The safest route is restoring a backup made before the compromise. If you are not sure when it started, an older backup may already contain the problem. If there is no clean backup, the site is rebuilt from WordPress, theme and plugin files downloaded again from the official source, with the content checked.
- Update everything. WordPress, themes and plugins to their latest versions. Plugins that are no longer maintained are replaced or removed.
- Remove what you do not recognise. Unknown users, plugins, themes and files. Check the user list directly in the database too, not only in the admin dashboard.
- Look for anything left behind. Attackers usually leave a way back in: scheduled tasks (cron) in WordPress or on the server, modified WordPress core files, code added to the active theme, plugins hidden in the mu-plugins folder, new rules in .htaccess. Compare the core files with the official release.
- Ask search engines for a review. After cleanup, request a new review in the tools for site owners, for example Google Search Console, so the warnings are removed. Ask your hosting company to reactivate the account if it was suspended.
Personal data: when you must notify
If the site holds personal data, such as customer accounts, orders or messages sent through forms, and that data may have been exposed, legal duties come into play. What follows is general guidance, not legal advice; check your specific case with your lawyer or data protection officer.
- GDPR. Article 33 of Regulation (EU) 2016/679 requires you to notify the supervisory authority within 72 hours of becoming aware of a personal data breach. In Romania, that authority is ANSPDCP (dataprotection.ro).
- NIS2. If your company is an essential or important entity under Romania's OUG 155/2024, significant incidents are reported separately to DNSC through the PNRISC platform: an early warning within 24 hours, a notification within 72 hours and a final report within one month of the notification. The EU directive sets the same 24 hours, 72 hours and one month (NIS2, article 23(4)).
- One does not replace the other. NIS2 reporting does not replace the duties in GDPR articles 33 and 34 (OUG 155/2024, art. 62(4)).
The evidence copy from step 2 helps here as well: it shows what data was on the server and what was accessed. If you are not sure whether NIS2 applies to your company, use the free NIS2 check.
What we do, and what we do not
To be clear: we do not offer incident response or cleanup of infected sites. During an active incident, call your hosting company or IT provider first.
Where we can help is once the site has been cleaned:
- The security audit looks for how they could have got in and what else is exposed: vulnerable plugins, open admin pages, files and backups left public, forgotten sub-sites, keys left in code, email without SPF or DMARC, and staff accounts that have appeared in data leaks. You get evidence and an ordered fix plan. For a small company, from €1,000 before VAT.
- Monthly monitoring repeats the check every month and emails you within one working day when a newly published weakness affects your systems or a staff account appears in a new leak. From €50 a month.
How to prevent it happening again
- Update WordPress, themes and plugins regularly, and keep only the plugins you actually need.
- Install plugins and themes only from official sources; "free" copies of paid plugins often come with hidden code.
- Give everyone their own account with the least rights they need, and switch on two-step verification for every admin.
- Remove the accounts of former staff and contractors as soon as they leave.
- Run automatic backups, keep them away from the website's server and test a restore from time to time.
- Restrict access to the admin page, for example by IP address, where you can.
- Delete test sites and old copies left on the server or on sub-sites.
- Run through the basics now and then; the guide is my business website secure? has the full 15-minute list.
Last updated: 22 November 2026.