WordPress Security Audit

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.

Discuss a project

What the audit covers

01

Plugins and themes

Versions, known vulnerabilities, abandoned components and what to replace them with.

02

Custom code

Input validation, escaping, nonces and capability checks, SQL queries, file uploads and AJAX/REST endpoints.

03

Users and access

Administrator accounts, roles, passwords, two-factor login and access for contractors.

04

Configuration

wp-config.php, file permissions, debug mode, XML-RPC, REST API exposure and security headers.

05

Server and hosting

PHP version, directory listing, backups, SSL and what is publicly reachable.

06

Signs of compromise

Unknown files, injected scripts, spam pages and suspicious scheduled tasks.

How it works

  1. 01

    Scope

    we agree what is checked — the whole site or only custom code — and in which environment.

  2. 02

    Access

    a copy of the site or read-only access; production is not touched without need.

  3. 03

    Analysis

    automated scanning plus manual code review, using AI tools to speed up reading large codebases.

  4. 04

    Report

    every finding with its risk level, how it can be exploited and how to fix it.

  5. 05

    Fixes

    on request I fix the issues and re-check the site.

Why an audit pays off

01

Cheaper than recovery

Cleaning up after a hack, lost sales and search penalties cost far more than finding the hole in advance.

02

Before launch or handover

An audit is the right moment when a site changes developers, gets new custom code or starts taking payments.

03

A clear plan

You get priorities instead of a long list: what to fix today, this month and later.

Price

The price depends on the size of the site and the amount of custom code and is fixed in advance after a short call.

Express audit

Plugins, configuration and access

  • Plugin and theme vulnerability check
  • Users, roles and access review
  • Configuration and server settings
  • Short report with priorities
Discuss a project

Full code audit

Express audit plus custom code

  • Everything in the express audit
  • Manual review of custom themes and plugins
  • WooCommerce, payments and integrations
  • Detailed report and fix plan
  • Re-check after fixes
Discuss a project

Frequently asked questions

Do updates replace an audit?

No. Updates close known holes in public plugins, but not problems in custom code, settings or access rights.

Can the audit be done without production access?

Yes, on a copy of the site. Access to production is only needed to check server settings.

How long does it take?

An express audit usually takes a few days, a full code audit one to two weeks depending on the code size.

Will the site be 100% secure afterwards?

No audit can promise that, but closing the found issues removes the most likely attack paths.

Contact

Let's talk about your project

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