How to monitor WordPress vulnerabilities across sites
WordPress does not provide a central vulnerability monitor for a group of sites. For a few sites, review Updates and Site Health and run WPScan on a schedule; for a larger fleet, use a dashboard that scans every site and alerts you when a known issue appears.
- 01Make a site inventory
- 02Check each site’s built-in warnings
- 03Run a manual WPScan check
- 04Schedule and review the checks
- 05Triage and fix findings
- 06Use a central dashboard for a fleet
What you need
- Administrator access to each WordPress site
- A list of site URLs and the components you manage
- A server or workstation where WPScan and a scheduler can run
- Backups or a staging process for testing updates
Make a site inventory
List every site, its owner, URL, WordPress version, active plugins and active theme. Include staging sites if they share production code, and record premium components separately because their update channels may not appear in the WordPress.org updater.
Mark sites that are behind a firewall, require a login, or block external requests. These conditions can make an outside scan incomplete rather than clean.
Check each site’s built-in warnings
On each site, open Dashboard > Updates and Tools > Site Health. Update WordPress, plugins and themes that have known fixes, and remove software that is not used. WordPress can apply minor and security core releases automatically, but plugin and theme auto-updates must be enabled individually where appropriate.
This is a useful manual check for a small number of sites, but it is not a vulnerability database or a central alerting system.
Run a manual WPScan check
Install WPScan on a controlled server or workstation, create an API token, and run a check for each site. A typical command is wpscan --url https://example.com --enumerate vp,vt --api-token YOUR_API_TOKEN --format json --output example-com.json. The vp and vt options check for vulnerable plugins and themes, while the scan also checks the WordPress installation.
Only scan sites you own or are authorised to assess. Keep the JSON output with the scan date so you can tell whether a finding is new, fixed or still present.
Schedule and review the checks
Put the WPScan command in a server-side scheduler and run it daily or at least weekly. Store results outside the public web root and send failures to an address someone actually monitors. If you use the free WPScan API allowance, remember that the API can make one request for WordPress, each detected plugin and each detected theme; a fleet can exhaust the daily allowance quickly, leaving you with scan output but no current vulnerability data.
Do not treat a missing report as a clean result. Check the scheduler, API response, DNS, SSL access, firewall logs and the site’s ability to accept external requests. The common Friday failure is a disabled WP-Cron or blocked loopback request, which stops scheduled checks without making the site look broken.
Triage and fix findings
For every finding, record the affected site, component, installed version, severity, fixed version and owner. Update to the fixed version after taking a backup and checking compatibility. If no fix exists, consider disabling or removing the component, restricting exposure, or applying the vendor’s temporary mitigation.
After updating, visit important pages, test forms and logins, and run the scan again. A scanner reports known component vulnerabilities; it does not prove that a site has not already been compromised, so investigate suspicious changes separately.
Use a central dashboard for a fleet
When you manage more than a handful of sites, the fast route is a central WordPress management dashboard with a vulnerability-checking extension. The MainWP Vulnerability Checker Extension runs scheduled checks across connected child sites, groups findings in the MainWP Dashboard, and shows the affected component, severity and fixed version. It can also send email or dashboard alerts for new non-ignored findings.
Install the free MainWP Dashboard plugin on the control site, connect the child sites, install the Vulnerability Checker Extension, choose the vulnerability provider and configure the schedule and notification settings. Then confirm that a test scan has a current last-check time. Keep checking the result rather than assuming that an enabled schedule ran: MainWP support notes that notification emails are sent after a scheduled cycle, not necessarily after a manual check, and only when relevant findings remain.
Let MainWP Vulnerability Checker Extension do it
Scheduled WPScan checks across MainWP sites with alerts and remediation details; ideal for agencies managing multiple WordPress installs.
Sources
- wordpress.org /documentation/article/updating-wordpress/?utm_source=openai
- kali.org /tools/wpscan/?utm_source=openai
- github.com /wpscanteam/wpscan/wiki/WPScan-User-Documentation/f155ade9ac…
- wordpress.org /plugins/wpscan/?utm_source=openai
- mainwp.com /add-on/vulnerability-checker/?utm_source=openai
Questions
- Can WordPress monitor vulnerabilities across several sites by itself?
- No. WordPress can show update notices and Site Health results on each individual site, but it does not provide a central vulnerability dashboard for a group of installations. You can run WPScan separately from a server and schedule those commands, or use a management system that connects the sites and collects vulnerability results in one place.
- Is checking the WordPress Updates screen enough?
- No. The Updates screen shows available updates, but it is not a complete vulnerability-monitoring process. A security database may identify a vulnerability before or after an update notice appears, and premium or abandoned components may need separate checking. Use Updates and Site Health as part of the routine, then compare installed versions with a maintained vulnerability database.
- Why does WPScan show no vulnerability data?
- WPScan needs a valid API token to retrieve vulnerability information from its database. The API allowance is also based on requests for the WordPress version and detected plugins and themes, so a large site or fleet can reach its limit. Check the scan output for API errors, confirm the token, and do not confuse a completed scan without vulnerability data with a clean result.
- What should I do when a vulnerability has no fixed version?
- Treat it as an open remediation item rather than ignoring it. Check the component author’s advisory, remove or disable the affected plugin or theme if practical, and apply any documented mitigation while you look for a maintained replacement. Record the decision and review it again because a fixed version may be released later.
- Will a vulnerability scanner tell me if my site is hacked?
- No. A vulnerability scan compares detected WordPress, plugin and theme versions with known vulnerability records. It does not prove that malicious code, unauthorised users or altered files are absent. If a site is exposed or a finding is severe, back it up for investigation, review access and file changes, and use a separate malware or integrity check before declaring it clean.