Work/Maintenance, Fixed

Taking 200+ WordPress sites from 99 critical vulnerabilities to zero

Jimmy Tran · 2026 · 3 min read

Aug 10Maintenance dashboard before
Sep 15Maintenance dashboard after

With 200+ client WordPress sites, updates at EOS happened whenever someone found the time. In August 2026 I put the whole fleet on one maintenance dashboard and connected AI to it, so routine updates run on their own and only the problems that need a person reach one. By mid-October, critical vulnerabilities were down from 99 to zero.

Company
EOS Healthcare Marketing
Role
Lead developer
Timeline
Aug to Oct 2026
Stack
WP Umbrella, MainWP, MCP

Maintenance, Fixed at a glance

  • Critical vulnerabilities fell from 99 to zero
  • Every vulnerability closed, medium and low ones included
  • About 10 hours a week of manual update work now runs through automation

Where the fleet stood

There was no update routine. Core, theme and plugin updates waited until someone had a reason to log into a site, and across 200+ sites that rarely happened.

On August 10 I connected every site to WP Umbrella and took a baseline. The fleet had 157 pending updates and 99 critical vulnerabilities. Some sat in plugins like Slider Revolution where no patched version existed, so updating alone would never close them. The security view scored the fleet 50 out of 100, with 96 sites flagged.

WP Umbrella update dashboard on August 10: 157 updates and 99 critical vulnerabilities
August 10: 157 pending updates, 99 critical vulnerabilities, 19 automations.
WP Umbrella security dashboard showing 96 sites with concerns
The starting security picture: 96 sites with concerns and a protection score of 50/100.

Letting automation handle the routine

WP Umbrella and MainWP both expose MCP servers, which let an AI agent work through them directly. I connected AI to both. It runs the safe updates, checks each site visually before and after to catch layout breaks, and watches the vulnerability and uptime alerts. Anything that fails a check or has no safe update comes to me.

Between August 10 and September 15, the number of active update automations went from 19 to 44.

Working the list down

With routine updates handled, I worked through the vulnerability list the dashboard surfaced. One morning pass on September 15 closed 22 issues by itself, taking critical vulnerabilities from 30 to 23 and medium or low ones from 53 to 38.

WP Umbrella update dashboard on September 15: 3 updates and 23 critical vulnerabilities
September 15: 23 critical vulnerabilities left, down from 99.

I kept going through the rest of the list. By October 14 the fleet had zero vulnerabilities of any severity and five pending updates.

Where it landed

99 → 0

critical vulnerabilities

Aug 10 to Oct 14

273 → 0

total vulnerabilities

critical, medium and low

157 → 5

pending updates

Aug 10 to Oct 14

19 → 38

active automations

Aug 10 to Oct 14

10+ hrs

saved per week

estimate

WP Umbrella update dashboard on October 14: zero vulnerabilities
October 14: zero vulnerabilities of any severity, 5 pending updates, 38 automations.

Next case study

EOS Company Brain →

Every AI tool at the agency started from zero. I built one place that holds what the business knows, so the AI starts with it.

Work with me

Have a fleet of sites that needs this? Let's talk.

jimmytran935@gmail.com