Plugins and themes
Versions, known vulnerabilities, abandoned components and what to replace them with.
Find the weak spots before attackers do.
Most hacked WordPress sites are not broken through WordPress itself but through an outdated plugin, a forgotten admin account or custom code written without security in mind. An audit shows exactly where your site is vulnerable and what to fix first.
Versions, known vulnerabilities, abandoned components and what to replace them with.
Input validation, escaping, nonces and capability checks, SQL queries, file uploads and AJAX/REST endpoints.
Administrator accounts, roles, passwords, two-factor login and access for contractors.
wp-config.php, file permissions, debug mode, XML-RPC, REST API exposure and security headers.
PHP version, directory listing, backups, SSL and what is publicly reachable.
Unknown files, injected scripts, spam pages and suspicious scheduled tasks.
we agree what is checked — the whole site or only custom code — and in which environment.
a copy of the site or read-only access; production is not touched without need.
automated scanning plus manual code review, using AI tools to speed up reading large codebases.
every finding with its risk level, how it can be exploited and how to fix it.
on request I fix the issues and re-check the site.
Cleaning up after a hack, lost sales and search penalties cost far more than finding the hole in advance.
An audit is the right moment when a site changes developers, gets new custom code or starts taking payments.
You get priorities instead of a long list: what to fix today, this month and later.
The price depends on the size of the site and the amount of custom code and is fixed in advance after a short call.
Plugins, configuration and access
Express audit plus custom code
No. Updates close known holes in public plugins, but not problems in custom code, settings or access rights.
Yes, on a copy of the site. Access to production is only needed to check server settings.
An express audit usually takes a few days, a full code audit one to two weeks depending on the code size.
No audit can promise that, but closing the found issues removes the most likely attack paths.

Contact
An AI agent, an automation, a website improvement or a full rebuild — describe the task in a few lines and I will reply within one business day.
Tallinn, Estonia · working remotely across Europe
The site does not use cookies. Visit statistics are collected without them. Learn more