WordPress security audit for businesses: what it is, what it covers and when you need one
By Kike Gandia · Co-Founder & CEO, OSCP · Last updated:
WordPress powers more than 40% of the world's websites. It also tops the statistics for compromised CMS platforms. Not because it is inherently insecure, but because its ecosystem of third-party plugins, themes and configurations creates a vast attack surface that automated tools and routine maintenance simply do not cover well enough.
What a WordPress security audit is
A WordPress security audit is an offensive technical assessment that simulates the behavior of a real attacker against a WordPress installation. It goes beyond scanning version numbers: it analyzes the authentication logic, third-party extensions, server configuration, file permissions, exposed APIs and application flows that an automated scanner cannot evaluate.
The outcome is an inventory of real vulnerabilities backed by evidence, classified by severity, together with a remediation plan prioritized by business impact.
What a technical WordPress security audit covers
Third-party plugins and themes: A review of every active extension against known CVEs (WPScan DB, NVD) and a code audit of custom extensions where available. Third-party plugins are the most common entry vector in WordPress compromises.
Admin panel (wp-admin): Exposure without additional authentication, brute force, user enumeration, lack of MFA and permissive settings that ease unauthorized access.
API endpoints: XML-RPC (enabled by default on many installations) and the WordPress REST API, with endpoints that expose users, content or metadata without authentication.
Forms and file uploads: Testing for stored XSS, SQLi, path traversal and remote code execution through contact forms, file-management plugins and upload areas.
Server configuration: HTTP security headers, file permissions (wp-config.php, .htaccess), direct access to the /wp-content/uploads directory and PHP settings that amplify the impact of vulnerabilities.
Roles and users: Enumerable administrator accounts, dormant accounts with elevated privileges, the absence of a password policy and open-registration settings.
What routine web maintenance does not cover
Updating plugins and themes resolves known vulnerabilities that already have a published patch. It does not detect:
- Malicious code injected into already-updated plugins or themes
- Vulnerabilities in custom plugins or bespoke development
- Misconfigurations of the server or hosting environment
- Web shells or backdoors planted during earlier compromises
- Vulnerable business logic specific to the installation
- Exposed API endpoints that are not part of any published CVE
An automated scanner such as WPScan or Wordfence does what it can with public data. A manual penetration test runs real intrusion tests against how the system behaves under attack.
WordPress audit vs automated scanning vs web maintenance
The three services are often confused, and they cost very different amounts. This is the real difference:
| Web maintenance | Automated scanning | WordPress security audit | |
|---|---|---|---|
| What it does | Updates core, plugins and themes | Checks versions against public CVEs | Simulates a real adversary's attack |
| Detects known CVEs | Only if a patch has been applied | Yes | Yes, and exploits them to measure impact |
| Vulnerabilities in custom code | No | No | Yes |
| Privilege escalation and business logic | No | No | Yes |
| Active web shells and backdoors | No | Partial | Yes |
| Server and hosting configuration | No | Partial | Yes |
| Reproducible evidence (PoC) | No | No | Yes |
| Report for management and auditors | No | Technical list | Executive + technical + remediation plan |
Maintenance and scanning are necessary, but they solve the known problem. The audit covers what neither of them can see: custom code, application logic and environment configuration.
WordPress security audit checklist
These are the controls a technical audit reviews and how each one is checked. You can also use it to evaluate a provider's proposal: if a row is missing, ask why.
| Area | What is checked | How it is tested |
|---|---|---|
| Core, plugins and themes | Versions with known CVEs, abandoned or unsupported extensions | Full inventory checked against vulnerability databases, plus controlled exploitation of what is found |
| Custom code | In-house plugins and themes: injection, access control, file uploads | Code review and manual testing of every entry point |
| Authentication | Brute force, user enumeration, MFA, password recovery | Controlled attacks against wp-login, XML-RPC and login forms |
| REST API and XML-RPC | Endpoints that expose users or content without authentication | Direct requests to every registered route |
| Roles and permissions | Too many administrators, dormant accounts, escalation between roles | Testing with users in different roles |
| Server and hosting | wp-config.php permissions, directory listings, headers, PHP version | Configuration review and testing from the outside |
| Integrity | Web shells, backdoors and injected code from earlier compromises | File comparison against the official versions and searches for malicious patterns |
| WooCommerce, if applicable | Checkout, orders, payment gateway and customer data | Tampering with prices, quantities and order statuses |
Free or AI-powered WordPress audit? What it detects and what it doesn't
Some free scanners are worth running: WPScan, in its command-line version, with a free plan for its vulnerability database limited to a number of daily requests, or the scanner built into security plugins such as Wordfence. There are also services marketed as AI audits. They all share the same fundamental limit: they compare what they see from the outside with vulnerabilities that have already been published.
| Free or AI-automated scanner | Manual audit | |
|---|---|---|
| Plugin versions with a public CVE | Yes | Yes |
| Confirms whether the flaw is exploitable in your installation | No | Yes |
| Vulnerabilities in in-house plugins or themes | No | Yes |
| Business logic and escalation between roles | No | Yes |
| Backdoors from an earlier compromise | Partial | Yes |
| False positives | Frequent | Ruled out before the report |
AI helps sort and summarize findings, but it does not replace someone who tests whether a flaw can actually be exploited. The practical recommendation: run a free scanner as a first filter and commission a manual audit when the site handles customer data or payments, or is a major sales channel.
Scope, duration and cost of a WordPress security audit
The price of a WordPress audit depends on the number of active extensions, the amount of custom development and whether e-commerce is in scope. Indicative ranges for a business installation:
| Installation type | Typical scope | Duration |
|---|---|---|
| Standard corporate site | Up to ~20 plugins, no custom development | 2-3 days |
| Corporate site with in-house development | Custom plugins and themes, integrations | 3-5 days |
| WooCommerce / online store | Checkout, payment gateways, customer data | 4-6 days |
| Multisite or multiple environments | Network of sites, shared roles | Custom |
On price, this site's pentesting calculator puts an audit of a CMS such as WordPress at €1,300 to €3,900 for a small scope, €2,000 to €6,000 for a medium one and €3,400 to €10,200 for a large one. A standard corporate site usually lands at the low end of those ranges; a WooCommerce store with in-house development, at the high end.
Every audit is quoted after a 20-minute scoping call: without access to the plugin inventory and the real size of the installation, any fixed figure is a blind estimate. We send a proposal within 24 hours.
What the WordPress audit report includes
The deliverable has to serve two different audiences, which is why it comes as two documents:
- Executive report: overall risk level, the three or four issues that matter most and the decision each one requires, without jargon.
- Technical report: every vulnerability with its severity (CVSS), reproducible evidence, steps to reproduce it and the specific fix, ordered by priority.
- Remediation plan: what to fix first, who should do it and what can be solved with an update versus what requires changing code.
- Retest, where agreed for the project: once the fixes are applied, we verify that the critical vulnerabilities have been closed.
A report that only lists outdated plugins with no evidence of exploitation is scanner output, not an audit.
When your company needs a WordPress security audit
- Before launching a corporate website, portal or shop built on WordPress that handles sensitive data
- When the site has grown in plugins and custom development without systematic security review
- After spotting unusual behavior: redirects, unauthorized content, drops in organic traffic caused by SEO spam
- To meet internal audit, ENS, ISO 27001 or sector-specific compliance requirements
- When your hosting provider, insurer or enterprise client requires evidence of security testing
- After an incident, or as part of the response and remediation process
FAQ
How long does a WordPress security audit take?
Between 2 and 5 business days for an installation of medium complexity. It depends on the number of active plugins, custom development, exposed endpoints and the agreed depth of the assessment.
Can the audit be run on the production environment?
Yes, although the recommended approach is to work on a clone of production (staging) to avoid any impact on availability. If we work on production, we schedule the more invasive tests outside peak-traffic hours.
Does the audit also cover WooCommerce?
If the installation includes WooCommerce, we audit it within the same scope: checkout security, order management, payment gateway integration and access to customer data. We also cover WooCommerce-specific plugins.
How much does a WordPress security audit cost?
It depends on the number of active plugins, custom development and whether an online shop is in scope. As a reference, €1,300 to €3,900 for a small scope, €2,000 to €6,000 for a medium one and €3,400 to €10,200 for a large one. A standard corporate site takes 2-3 days; an installation with custom development or WooCommerce, 4 to 6. We agree the scope on a 20-minute call and send a proposal within 24 hours.
Is there a free WordPress security audit?
There are free scans, not audits. Tools such as WPScan or the Wordfence scanner detect plugin versions with published vulnerabilities and make a good first filter. What they do not do is confirm whether the flaw is exploitable in your installation, review custom code or look for backdoors from an earlier compromise: that takes a manual audit.
Is a WordPress audit done with artificial intelligence any good?
As a complement, yes: AI speeds up the inventory and helps prioritize. As a substitute, no: an automated analysis, with or without AI, compares what it sees with known vulnerabilities and generates false positives. Confirming what is exploitable, testing your site's logic and filtering out the noise still takes a pentester.
How often should the audit be repeated?
Once a year as a baseline, plus after any significant change: a hosting migration, adding a critical plugin, new custom development or opening a payment channel. If the site is the main sales channel, every six months is the norm.
How is it different from hiring web maintenance?
Maintenance keeps the software up to date; the audit checks whether that specific installation is exploitable. The two are complementary: most of the compromises we analyze happen on sites whose maintenance is perfectly up to date, through vulnerabilities in custom code or environment configurations that no update fixes.
Related service
CMS pentesting and audit service
Related content
- GDPR and LOPDGDD audit
- WordPress pentesting
- WordPress plugin security
- WordPress hardening for businesses
- CMS security vs web maintenance
- Joomla security audit
- Penetration testing for businesses
- Cybersecurity audit services
- Cybersecurity for SMBs