For agencies, hosts and MSPs
Answer every client with evidence.
Last updated:
Fleet Triage gives each client site a clear call (go, mitigate, patch, or offline until fixed) with a one-page summary you can forward. $990 for a 10-site pilot, then $99 a site, graduated: $79 from site 50 and $59 from site 200.
Doing it in-house? The agency guide to PHP2Shell triage walks through the same go/no-go method, free.
One table, one decision per client
Many hosts reported patching their managed plans, but servers you or your clients run are yours to patch (source: GoDaddy). A version number can’t tell you which sites are fixed (source: AlmaLinux). Every site gets one of four calls, with the evidence behind it.
| Client site | Hosting and PHP | What we saw | Evidence | Call | Next step |
|---|---|---|---|---|---|
bakery.example |
Shared host that reported patching | Host’s written confirmation | Level 3: host-attested | Go | Confirm the CVE-2026-115560 setting with the host |
shop.example |
Your VPS, PHP 8.4.27, WooCommerce | Fixed release running; CVE-2026-115560 setting missing | Level 1: runtime-verified | Mitigate | Apply the setting, restart PHP, add a firewall rule |
clinic.example |
Your VPS, PHP 8.1 Ubuntu package | Package changelog cites both CVEs | Level 2: package-verified | Go | Plan the move off 8.1 (end-of-life) |
lawfirm.example |
Your VPS, PHP 8.3.30 upstream build | Below the fixed release (8.3.36) | Level 1: runtime-verified | Patch | Update to 8.3.36 and restart PHP |
legacy.example |
Client’s own server, PHP 5.6 | No vendor backport available | Level 1: runtime-verified | Offline until fixed | Maintenance page now; quoted upgrade |
Scroll the table sideways to see every column.
- Mitigate
- A configuration change and a firewall rule close the gap.
- Patch
- A package update is needed, then a restart.
- Offline until fixed
- End-of-life PHP with no backport, and exposed (source: Beazley Security Labs). Your client decides when to go back online.
How fleet triage works
Read-only from start to finish. Within 2 business days for up to 50 sites.
-
Step 1: Send the site list
You
With written proof that you can authorize work on each client’s site. Every end client signs our authorization form.
-
Step 2: Verify the domains
You
A DNS record per domain, or one delegated verification where you run your clients’ DNS.
-
Step 3: Collect the evidence
Our delivery system
A passive exposure check for every site, written confirmation from hosts that patched, and a read-only check on servers you manage.
-
Step 4: Approve the calls
Approver of Record
The Approver of Record reviews every row before you see it.
-
Step 5: Deliver the pack
Approver of Record
A sortable fleet summary (CSV and PDF), a one-page note per client you can forward, and the next step for every site that isn’t “go”.
Partner terms
One published price list, under your brand alongside ours.
- Agency Fleet Triage, graduated (sites 1–49 / 50–199 / 200+)$99 / $79 / $59 per site; $990 for the 10-site pilot; no partner discount on top
- Patch Verification for flagged sites$472 per server, every server, +$120 per extra site, capped at $1,432 per server (20% off)
- EOL Readiness Report$232 per CMS site / $392 per custom app (20% off)
- Verification Plan$792 per server per year, +$120 per extra site (20% off)
- ReportsCo-branded
The partner discount is at most 20%, and only on fixed-price single-client jobs: Patch Verification, the EOL Readiness Report and the Verification Plan. It never stacks on the graduated Fleet prices, which are already wholesale.
Graduated, like tax brackets: each site is priced by its own band, so a bigger order never costs less.
Non-negotiable
Every end client signs our authorization form, and it can’t be white-labelled. It protects your clients, and it protects you.
Hosts and MSPs
Customers on end-of-life PHP need an upgrade path before December 31 (source: php.net supported versions). The EOL Readiness Report tells each one what the move involves.
Your website, accounted for.
Clients are asking now.
Tell us how many client sites you look after, and we’ll set up a short call.
Sources
Every figure and quotation on this page links to its primary source. All of them, with the date we last checked each: full wording and methods.
-
Who patches PHP: managed hosting vs your own server S-05b
GoDaddy Hostinger SiteGround WP Engine WordPress.com Xserver Sakura Internet Lolipop
Last checked: October 23, 2026
-
`php -v` can't prove you're patched S-09
AlmaLinux CloudLinux Xserver Red Hat Sucuri The Hacker News TuxCare
Last checked: October 23, 2026
-
CVE-2026-115560: not fixed by the 21 Oct releases S-02b
php.net advisory on CVE-2026-115560, October 23, 2026 CERT-EU BleepingComputer Cloudflare
Last checked: October 23, 2026
-
No official fix for 8.1 and older S-03
Beazley Security Labs The Hacker News
Last checked: October 23, 2026
-
PHP 8.2 end of life S-32
Last checked: October 23, 2026