wp2shell: more than a month later. Confirm 6.8.6, 6.9.5, 7.0.2. Patched is not clean.

Read the advisory
Monitoring Dictionary

Security audit

Definition

A security audit is a structured review of a site’s risks, misconfigurations, and recommended fixes.

Also called: WordPress security audit

Why it matters for WordPress

Gut feel is not a plan. An audit turns “we should be more secure” into ordered work: outdated plugins, leftover admins, missing backups, open XML-RPC, weak login controls. Agencies use the same pass before launch or after a scare.

How it shows up in practice

  • Scored security tests with pass/fail items you can re-run
  • A spreadsheet of plugin versions next to known CVEs
  • External review notes before go-live or after a compromise
  • Monthly checks on client sites where nobody watches the dashboard daily

What to do

  1. Inventory software, users with elevated roles, and backup restore proof.
  2. Run automated tests, then verify anything that looks wrong (false positives happen).
  3. Fix high-impact issues first: admin access, known CVEs, missing restores.
  4. Re-run after changes so the report matches the live site.

In WP Security Ninja

Security tests give a structured hardening checklist you can re-run after fixes. Combine them with the vulnerability scanner so configuration issues and known CVEs show up in one review cycle. Full walkthrough: WordPress security audit guide.

Go deeper

Want the full walkthrough?

This page stays short on purpose. The guide covers steps, examples, and what to check on a live WordPress site.

Open full guide

Nearby ideas in the dictionary

All terms →

Larger screenshot