WordPress security,before something happens.
We review your WordPress site's security, close the weak spots and get updates working. If the site has already been hacked, we clean out the malware and close the backdoors so the attack does not come back.
A default WordPress setup leaves several doors open: usernames are visible to anyone, passwords can be guessed without limit, and there is no firewall and no security headers. Most of this can be fixed in one go.
What we do.
When the project is done you get a PDF audit with guidance for the future: what the default WordPress setting was, what we changed it to and why it matters. A security fix is a one-off job for a one-off fee – no monthly fee and no contract.
Security audit
- Exposed usernames and log files
- Outdated plugins and themes
- Configuration and server check
- Written report of findings
Hardening
- Firewall and malware scanning
- Login protection and 2FA
- Security headers and HTTPS
- Code editor and XML-RPC disabled
Updates
- Automatic security updates
- Major updates after testing
- Unused software removed
- Follow-up scan
Cleanup
- Malware removal
- Finding and closing backdoors
- WordPress core reinstall
- Password reset
Check your site yourself.
Three checks you can do right now, with no technical knowledge. Replace yoursite.com with your own address.
1. Usernames
Open yoursite.com/wp-json/wp/v2/users in your browser. If you see a list of users, your usernames are public and an attacker only has to guess the password.
2. Version information
Open yoursite.com/readme.html. If a WordPress introduction page opens, anyone can see what software your site runs. With outdated software, its known weaknesses can be exploited straight away.
3. Security headers
Enter your site's address at securityheaders.com. A low grade (D or F) means the browser security headers are missing.
If even one of the three gives a bad result, the site is worth a review. Write to: oliver@no11.ee
If the site is already hacked.
Deleting the visible malware is not enough. If a backdoor stays on the site, the attacker returns even after the passwords are changed. Cleaning a hacked WordPress site takes three steps.
1. Cleanup
We clean the infected files and delete the modules the malware installed and the administrator accounts it created. We replace the WordPress core files with clean ones from the official source, so nothing altered remains in the platform's own code.
2. Closing the backdoors
We find where the attacker left a way back in – for example a file placed on the server, or a hidden piece of theme code that allows logging in with a secret password. Then we change the WordPress, database and FTP passwords.
3. Hardening and monitoring
We add a firewall and login protection, make two-factor login mandatory for administrators and switch on automatic updates. A follow-up scan confirms the cleanup has held.
Before and after.
The WordPress site of an Estonian company where nothing had happened yet. This is how it looked before and after hardening.
Frequently asked questions.
How much does a security fix cost?
A security fix is a one-off job for a one-off fee. There is no monthly fee and no contract. We give an exact price once we have looked at the site.
Is WordPress secure?
Yes, as long as the core, plugins and theme are up to date and the configuration is thought through. The large majority of WordPress break-ins go through outdated plugins whose vulnerability is already public.
Why is changing passwords not enough on a hacked site?
Because the attacker usually leaves a backdoor – a file or piece of code that lets them in with the new password too. The backdoor has to be found and removed first; only then does changing passwords help.
Why does two-factor login matter so much?
It is the only protection that still works when a password has leaked. On login the site asks for a code from an authenticator app on your phone as well as the password. Setting it up takes about two minutes.
Can automatic updates break the site?
WordPress security patches and smaller plugins update automatically. Larger components such as WooCommerce, WPML or Gravity Forms we update by hand after testing.
Is a security plugin enough on its own?
No. A firewall and scanning are one part. It matters just as much to remove unused plugins and themes, keep software up to date and limit what an administrator account can do.
Why hide the WordPress version number?
Attack bots look for sites by the known holes of a specific version. The less a site says about itself, the less often it becomes a target.