Know within minutes whether a disclosure affects you
Keep track of known plugin vulnerabilities across connected WordPress websites, review the affected sites and follow the patching work from one WPCentrify dashboard.
Plan prices to be revealed. Start free on one website today.
Updated
What is WordPress vulnerability monitoring?
WordPress vulnerability monitoring keeps checking the plugins, themes and WordPress version a site runs against newly published security holes, so you hear about a problem in software you already have instead of discovering it after an attack. New holes appear constantly: Patchstack counted 11,334 in the WordPress ecosystem in 2025, 42 percent more than in 2024.
WPCentrify highlights known vulnerabilities affecting connected websites and shows the available fixed version. Review findings and patch status in one place, then confirm the affected website has been updated.
WPCentrify vulnerability monitoring at a glance
- Review known-vulnerability findings and the available fixed versions.
- One finding per vulnerable plugin or theme, with the version that fixes it.
- Clears on its own once the site runs a fixed version.
- Update now from the finding, or let a rule apply such fixes automatically.
- Advisories marked as informational only are not raised as problems.
No maintained fix available? Our guide to abandoned WordPress plugins explains how to assess support status, reduce exposure and plan a safe replacement.
Periodic scanning is too slow for disclosure timelines
Vulnerability scanning on a weekly or nightly schedule made sense when disclosure and exploitation were separated by weeks. For widely deployed WordPress plugins, mass scanning for a newly disclosed flaw now frequently begins within hours of the advisory going public.
A scan that runs tonight tells you tomorrow morning about something attackers started probing yesterday afternoon. The scan is not wrong; the cadence is. And on a portfolio, the delay is multiplied by the number of sites carrying the same component.
A long list of findings is difficult to act on. Review which websites are affected, how urgent the issue is and what work is needed, then prioritize the response for the websites you are responsible for.
What ongoing vulnerability monitoring gives you
- Review newly identified vulnerability findings in the dashboard
- One issue affecting eleven sites shown as one item, not eleven rows
- Ranking by affected sites and what those sites do
- Exposure window measured from disclosure, not from detection
- Patch status tracked across the portfolio in one view
- Evidence retained for client reporting and audit
Review affected websites and follow the patching work
Keep known-vulnerability findings alongside Sentinel security monitoring so you can review the website risks and follow the appropriate next step.
Review affected components
See which connected websites need attention and which components are affected. Keep plugins current so the available checks can provide useful coverage.
Review known vulnerabilities
Review findings that identify the affected component and available fixed version, then confirm that the website no longer runs the affected version.
Consequence ranking
Use the finding priority and affected-site view to decide what to review first. Confirm the impact on the website before deciding the response.
Patched through safe updates
Patching runs through the same verified update workflow as anything else: restore point, patch, health and visual checks, automatic rollback on failure. Speed and caution stop being a trade-off.
What is monitored
Plugin and theme vulnerabilities
Known-vulnerability findings for supported components across connected websites.
Core and PHP versions
Sites behind on WordPress core or running end-of-life PHP, surfaced before a host forces the upgrade.
Portfolio grouping
A single vulnerable component across many clients presented as one item with one action, not scattered across site views.
Exposure windows
Time from public disclosure to patch applied, per issue and as a portfolio average. The number that actually measures your risk.
Payment path weighting
Disclosures affecting checkout or payment extensions ranked higher, because the consequence is direct revenue loss.
Client evidence
Every detection and patch recorded with timestamps in the change record, ready for the monthly report or a client asking how long they were exposed.
Why this and security scanning are different things
Vulnerability monitoring highlights known weaknesses in the components you use. It does not prove that a website is free from malware, so keep infection checks alongside it.
Security scanning answers whether a site has already been compromised: modified core files, injected content, unfamiliar files in uploads, unexpected administrator accounts. It is a forensic problem, and it is inherently noisier.
Both matter and they catch different things. Vulnerability monitoring is preventive and cheap to act on. Security scanning is detective and usually means something has already gone wrong. An agency running only the second is finding out too late.
What this does not do
- Runtime firewalling or request blocking
- Hands-on malware removal, which is a specialist service
- Detecting zero-day flaws with no published disclosure
- Custom or bespoke plugin code with no public advisory
- Server hardening, which sits with your host
Related
Portfolio security
How exposure is ranked and prioritized across every client.
Read moreSecurity scanning
Detecting compromise rather than predicting it.
See the featureWhat to do first when a WordPress site is hacked
Containment, assessment, cleanup and the conversation with your client, in order.
Read the checklistQuestions about vulnerability monitoring
Vulnerability monitoring highlights known weaknesses that need attention. Malware scanning investigates signs of an existing infection. Use both, then review the appropriate fix for the finding.
No, and nothing that works from public disclosure data can. It catches known flaws with published advisories, which is the overwhelming majority of what actually compromises WordPress sites. Zero-days exist but are not the common case for small business sites.
Bespoke code has no public advisory to match against, so it is not covered here. Code review and secure development practice are the answer for custom components, and it is worth knowing which of your sites carry them.
Minutes rather than weeks, because patching runs through the safe-update workflow with a restore point and automatic rollback. The thing that normally slows agencies down is fear of breakage, and that is exactly what verification removes.
Review the plugin findings in WPCentrify to see known vulnerabilities, affected websites and available fixed versions. Custom components and missing coverage need a separate review.
Thousands. Patchstack counted 11,334 new vulnerabilities in the WordPress ecosystem in 2025, 42 percent more than in 2024, which is why checking once a month is not enough.
Yes, if you choose to. From a finding you can press Update now, or create an automation rule that applies an update when it fixes a known security hole. The rule only applies updates that actually close the hole.
Close the gap between disclosure and patch
Review affected websites, prioritize the findings and verify your patching work from one dashboard.
Plan prices to be revealed. Start free on one website today.
Explore related Sentinel security features
Pair patching with the wordpress firewall in WPCentrify.
Reduce avoidable exposure with security hardening in WPCentrify.