How we count the numbers on this site
Some pages show live figures from the sites we look after. Each is an aggregate across every agency, over the last 90 days, refreshed nightly, and a figure stays hidden until it rests on at least 30 sites and 200 observations (findings, patches, rollouts or backup checks, whichever it counts).
What we promise about the data behind them is part of our Privacy Policy.
Every figure is
- An aggregate across every agency
- The last 90 days, refreshed nightly
- Hidden until 30 sites stand behind it
What each figure measures
| Figure | How it is counted |
|---|---|
| Sites that arrive with a known vulnerability | When a site joins, we check every installed plugin, theme and WordPress core version against known vulnerabilities. This is the share of sites that joined in the last 90 days where that first full scan found at least one. |
| Of those, sites with an actively exploited (CISA KEV) vulnerability | Of the sites that arrived with a vulnerability, the share where at least one is on CISA's Known Exploited Vulnerabilities list, meaning attackers are using it. We check against the list as it stands on the day the figure is computed. |
| Median time from a fix being released to patched | For each vulnerable component we updated to a fixed version, the hours from the advisory's publication to the update being applied. If the advisory came out before the site joined, the clock starts when the site joined. We use the advisory date because our data does not record when the fixed version was released; vendors usually publish the two together. The figure is the median, in whole hours. |
| Patches re-scanned and confirmed fixed | After we apply a security patch, we scan the site again. This is the share of security patches where that second scan confirmed the vulnerability no longer matches. Patches from the last 24 hours are left out, because their re-scan may not have run yet. |
| Vulnerabilities found with no fix available yet | Of all the vulnerabilities found on sites in the last 90 days, the share where the vendor had not yet released a fixed version. These can't be fixed by updating; the plugin has to be deactivated, replaced or protected another way. |
| Rollouts stopped and rolled back by the health gate | Every update rollout checks each site's health after updating, and rolls back automatically if a site breaks. This is the share of rollouts in the last 90 days where that happened on at least one site. |
| Backups verified | After each backup, we download every stored piece, decrypt it and check it against its fingerprint and the database hash. This is the share of those checks in the last 90 days that passed. Skipped checks are not counted. |
| Sites with a risky file exposed | The share of scanned sites where, in the last 90 days, we found a file that should never be public: an exposed .env file, a copy of wp-config.php, a database dump or site backup in the web root, or PHP code in the uploads folder. |
| Most-found vulnerable plugins | The free WordPress.org plugins found vulnerable on the most sites in the last 90 days, with the share of sites affected. |
The same figures are published as JSON.
Which plugins we name, what is left out and how an agency opts out: Privacy Policy, published statistics.
Try it on your own sites
14 days of every Business feature on up to 5 sites. Cancel before it ends and you pay nothing.