1. Red
  2. Learn
  3. Agencies and MSPs

Client security incident email template for agencies

Copy-paste email templates for agencies answering clients who ask 'are we affected?': five situations, the evidence each needs, and wording that survives a proof request.

By Timothy Lindblom, FounderPublished 4 November 20269 min readHow we check facts
On this page
  1. What must every client email contain?
  2. Which template do I send?
  3. Template A: what do I send when I have the evidence?
  4. Template B: what do I send when the host has not answered?
  5. Template C: what do I send when the site is exposed?
  6. Template D: when can I tell a client they are not affected?
  7. Template E: what do I send if something looks wrong?
  8. What phrases draw a request for proof?
  9. What should I attach to each email?
  10. When does an incident email turn into a breach notification?
  11. How often should I write, and who sends it?
  12. Where does a scan fit?

Answer each client with a status for their own site, in one of three words: confirmed, unknown or exposed. Send "confirmed" only with a fixed package or build name and a restart time after it, say "unknown" with a follow-up date when you hold neither, and never write "all sites are patched". Five templates follow, each with the evidence it needs.

FactDetailSource
Worked examplePHP2Shell: CVE-2026-109618 and CVE-2026-109619, CVSS 9.2, disclosed 21 October 2026PHP notice
Fixed upstream8.5.12, 8.4.27, 8.3.36, 8.2.35. Affected means below these on each branchGHSA-w8hw-w9fx-j79w
ScopeEvery PHP installation serving web requestsPHP notice
First attempt on record17 October 2026, AWS honeypots (vendor-claimed)AWS
Active exploitation per governmentExploited in the wild per open-source reporting, Canadian Cyber Centre update 2 (page updated 27 October)Canadian Cyber Centre
CISA KEVBoth CVEs added 26 October 2026, federal due date 29 OctoberCISA KEV
Checked4 November 2026this page

The templates use PHP2Shell because it is the question your clients have been asking since 21 October. Swap the CVE ids and the evidence line and they fit the next advisory. The portfolio side (the ledger, grouping sites by who controls PHP) is in the agency triage guide.

What must every client email contain?

Five things, in this order. Clients read the first two lines and forward the rest.

  1. The status for their domain, in one word.
  2. The evidence behind it, or the plain statement that you have none yet.
  3. What happens next, with a date.
  4. What you need from them, if anything.
  5. The window you checked for earlier activity.

One short paragraph on what the flaw is helps, because the client's contact is often not technical. The PHP project describes both CVEs as remote code execution in the PHP engine itself, which is why updating WordPress or a plugin does not close them. Say that once, early.

Which template do I send?

Pick by the evidence you hold for that domain, not by how the client feels.

What you hold for the domainStateTemplate
Package or build naming both CVEs, plus a restart or redeploy time after itConfirmed by owner evidenceA
The host has not given a build or a restart timeUnknownB
Version below the fix, or an end-of-life branch with no vendor backportDetected, exposedC
Proof the site runs no PHPNot affectedD
Anything odd in logs, files or accounts, or personal data possibly involvedUnder investigationE
Which client template to send, by the evidence held for the domain Does the site run PHP? No, and provable Template D Build + restart held Template A Neither held Template B or C Anything odd in logs? Add Template E
Choose the template from the evidence held for that domain. Template E is added to any of the others when the log review finds something.

Template A: what do I send when I have the evidence?

Use it only when the ledger row is complete. Debian's FAQ says it backports fixes into the shipped version, and Plesk's change log records the fix going into PHP 8.1.34, 8.0.30 and 7.4.33 with those numbers unchanged. So quote the build or package name, not the branch.

Subject: [domain]: PHP update confirmed, [date]

Hello [name], on 21 October the PHP project disclosed two serious flaws in PHP, the language your site runs on. Status for [domain]: confirmed. [Host or us] installed [package or build identifier], whose changelog names CVE-2026-109618 and CVE-2026-109619, and restarted the PHP workers serving your site at [time, timezone] on [date]. We have the record and can send it. We are also reviewing logs from 17 October for earlier activity and will write by [date] with the result. Nothing is needed from you.

Template B: what do I send when the host has not answered?

This is the common case. The honest note is short, names who you asked and sets a date. Hosts often run several versions side by side, and a cPanel server can assign a version per domain, so ask per domain. Our shared hosting page has the host-side question.

Subject: [domain]: PHP flaw, status unknown, update by [date]

Hello [name], two serious flaws in PHP were disclosed on 21 October. Status for [domain]: unknown. We asked [host] on [date] to confirm in writing which PHP build serves your site and when it was last restarted. We have no answer yet and will not tell you the site is updated until we do. We will write again by [date], whatever the reply. If you hold the hosting login, you can forward the question to [host] yourself.

Template C: what do I send when the site is exposed?

Say so plainly and ask for the decision you need. CERT-EU says to patch immediately or isolate internet-facing resources, and the UK NCSC says to consider taking a system offline if it cannot be mitigated. For branches 8.1 and older, php.net released nothing, but published source backports for 7.4, 8.0 and 8.1, and vendors ship their own.

Subject: [domain]: PHP update needed, please reply by [date]

Hello [name], [domain] runs PHP [version] on [host], which is below the fixed release for its branch. Status: exposed until updated. Options: (1) we update to [version] on [date] and test checkout and forms afterwards, (2) we move the site to a supported PHP branch, (3) the host applies a vendor fix and confirms the build. Please reply with 1, 2 or 3 and confirm we may make changes. Until then we are making no changes to your hosting.

Template D: when can I tell a client they are not affected?

Only when the site runs no PHP at all, shown by the build or hosting plan and not by an assumption. The PHP notice puts every installation serving web requests in scope, so a host saying "you are not affected" is not enough on its own. A static or Node.js site is outside this bug. Its third-party scripts and apps are a separate question.

Subject: [domain]: not affected by the PHP flaws

Hello [name], [domain] is built on [platform] and is served without PHP, which we checked in [build config or hosting plan] on [date]. The PHP flaws disclosed on 21 October therefore do not apply to it. We will tell you separately if anything else touching the site needs attention.

Template E: what do I send if something looks wrong?

Send this as soon as a log review finds an unexpected file, an unknown administrator or a scheduled task nobody created. AWS recorded its first honeypot attempt on 17 October and says it remains unclear whether any attempt would have succeeded on a real system, so an attempt in a log is not a compromise. Evidence on that specific site is.

Subject: [domain]: unexpected activity found, next update [time]

Hello [name], while reviewing [domain] from 17 October we found [one factual sentence, for example "an unfamiliar PHP file in the uploads folder created on (date)"]. We do not yet know whether it relates to the PHP flaws or whether anything was accessed. We have preserved the logs and have changed nothing. With your written agreement we will [next step]. Please tell us whether the site holds customer or personal data. Next update by [time].

What phrases draw a request for proof?

Agencies report clients who watched the news and now expect to hear "we patched PHP immediately" about their own site. A phrase like that invites the follow-up request for proof. Replace it.

AvoidWhyWrite instead
"All sites are patched"One statement for a portfolio hides per-domain differences"[domain] is confirmed: [build], restarted [time]"
"We are on PHP 8.3"A branch label; backports keep the numberThe build or package name
"Cloudflare protects you"Cloudflare calls its rule an additional layer and still says to patch"The WAF buys time while we update"
"You were not hacked"No source names a compromise either way"We reviewed logs from 17 October and found [result]"
"Nothing to worry about"CISA has listed both CVEs as exploited since 26 October, and the Cyber Centre reports exploitation in the wild"No confirmed compromise on your site at [date]"
"Fixed" with no timeA package nobody restarted keeps serving old code"Updated at [time]; workers restarted at [time]"

On restarts, Canonical says the application likely needs a restart or the system a reboot, and watchTowr says to restart every PHP worker. The restart time is the line clients do not know to ask for, so put it in.

What should I attach to each email?

Attach the one record that backs the status, and nothing else. A client's technical contact can forward it to their own auditor.

  • Template A: the changelog excerpt naming both CVEs and the service start time, or the host's written reply with its date.
  • Template B: the message you sent the host, with the date.
  • Template C: the version you saw and the option the client chose.
  • Template D: the build or hosting plan line showing no PHP.
  • Template E: the date range reviewed and what was and was not examined.

Am I affected? Which status can I give this client

A check from outside can read headers and version hints. It cannot see the package changelog, which runtime serves a virtual host, or when workers last started.

  1. Detected The site serves PHP and the version it shows is below the fixed release for its branch. Send Template C. Update and restart, or move the site, and tell the client it is awaiting a fix.
  2. Unknown The version is hidden, could be a backport, or you cannot tell which PHP serves the domain. Send Template B and chase the host for build and restart time.
  3. Confirmed by owner evidence You hold a package or build identifier naming both CVEs and a restart or redeploy time after it. Send Template A. Whether anything got in earlier is a separate question.

No scan, ours included, moves a site from "unknown" to "confirmed".

When does an incident email turn into a breach notification?

When personal data may have been involved. The GDPR text sets the pattern in Articles 33 and 34: a processor notifies the controller without undue delay, the controller notifies the supervisory authority within 72 hours where feasible, and high-risk breaches are communicated to the people affected. Whether your agency is a processor for a given client depends on your contract and its liability clauses.

That notification is a separate document from these templates; the customer breach email covers its wording and deadlines. Template E only tells the client early, in plain words, so they can start their own clock. Do not write "no data was accessed" until you have evidence for it. The full incident response steps covers preserving logs and rotating credentials, and this guide lists indicators.

How often should I write, and who sends it?

Write when the status changes and on the follow-up date you promised, even if the news is that nothing changed. Send from a named person at the agency, not a no-reply address.

  • Today: send Template B to every client whose evidence is missing, and Template A to those with a complete row.
  • By the date you promised: send the follow-up, using the same subject line so the thread holds.
  • When a host answers: move the client's status, forward the reply, and note the time received.
  • After the log review: tell every client the result, including "nothing found in the window we reviewed".

For a client with no technical contact, the ten minute response page can be forwarded as written. The wider picture is in the October 2026 tracker, and the other agency guides cover the rest of the client side.

Where does a scan fit?

Before you send "exposed" or "unknown", a scan can show you which clients' sites advertise an old version. The Red free scan reads the stack a site serves and matches each version to known vulnerabilities. One scan per domain, no card. It is a lookup: it can say a version is affected, not whether your setup is exposed, and it cannot see a backport, which runtime serves a virtual host, or whether workers restarted. Domain ownership is proved with one DNS TXT record, so the client or whoever holds their DNS does that step, and you should still hold their written agreement first. If you want this as a standing service, scans as an agency offering covers consent and the report. The full scan costs $100 per scan and is ordered from the dashboard once the free scan is done. Neither produces a "confirmed" for your client email.

Questions people ask

What do I tell clients who ask whether we patched PHP?

Tell them what you can show. If you hold a package or build name that lists both CVEs and a restart time after it, say the runtime serving their domain was updated on that date. If you hold only the host's word, say you have asked for written confirmation and give the date you will follow up.

Can I send one email to every client?

Send one explanation, but give each client a status for their own site. A cPanel server can assign a different PHP version to each domain, so one host answer can be true for one client and false for the next. A single 'all sites are updated' line is the sentence that draws a request for proof.

A client forwarded a scanner alert saying their site is vulnerable. How do I reply?

Answer with the evidence for that domain: the package changelog or build record and the restart time. Many scanners read the version banner, and distributions backport fixes without changing the number. Ask the scanner's operator to retest against the evidence, and if you hold none yet, ask the host.

Do I have to tell the client if I don't know yet?

Yes, and early. A short note that says unknown, names who you asked and gives a follow-up date costs less than a later correction. Clients who watched the news will assume the worst from silence.

When does an incident email become a breach notification?

When there is evidence that personal data was affected. Under the GDPR a processor tells the controller without undue delay, and the controller has 72 hours where feasible to notify the authority. Your contract decides who is which, so check it before you send that email.

Is it enough to say Cloudflare is in front of the site?

No. Cloudflare calls its rule an additional layer and still tells customers to patch. Traffic that reaches the origin by another route is not covered. Describe the WAF as time bought while the update is applied.

Sources

  1. PHP security notice, 21 October 2026, and 23 October follow-up (php.net)Fixed releases, scope (every PHP installation serving web requests), source backports for 7.4, 8.0 and 8.1, interim settings. Read 24 October 2026.
  2. GHSA-w8hw-w9fx-j79w: CVE-2026-109618 (php/php-src advisory)CVSS 9.2; affected means below 8.2.35, 8.3.36, 8.4.27 and 8.5.12. Read 24 October 2026.
  3. GHSA-6wmf-4rv5-p3rp: CVE-2026-109619 (php/php-src advisory)Says multiple workers and recycling reduce success per request but do not remove the condition. Read 24 October 2026.
  4. Amazon Threat Intelligence: PHP2Shell attempts in MadPot honeypots before disclosure (AWS Security Blog, 21 October 2026)Vendor telemetry. First attempt 17 October; AWS says it remains unclear whether any attempt would have succeeded on a real system.
  5. UK NCSC: critical security issue affecting PHP (21 October 2026, updated 23 October)Inventory PHP systems, internet-facing first; watch vendors that bundle PHP; consider taking a system offline if it cannot be mitigated.
  6. Canadian Centre for Cyber Security alert AL26-026 (update 2, page updated 27 October 2026)Update 2 reports open-source indications that both CVEs are exploited in the wild and notes the CISA listing; find products and containers that bundle PHP. Read 4 November 2026.
  7. CERT-EU security advisory 2026-018 (version 1.2, 23 October 2026)Patch immediately or isolate internet-facing resources; source patches exist for 7.4, 8.0 and 8.1.
  8. Cloudflare: WAF protections for the PHP vulnerabilities (updated 23 October 2026)Calls the WAF rule an additional layer and tells customers to patch their PHP.
  9. watchTowr: PHP2Shell FAQ (updated 23 October 2026)Vendor-claimed honeypot exploitation from 21 October; restart every PHP worker after updating.
  10. Debian security FAQ: backported fixes and version numbersDebian backports fixes to the version shipped in stable, so the number alone does not show whether a package is fixed.
  11. Canonical: PHP2Shell vulnerability fixes available (Ubuntu blog)Fixed package per release, for example 8.1.2-1ubuntu2.28 on 22.04; the application likely needs a restart or the system a reboot.
  12. Plesk Obsidian change log: PHP updates of 21 October 2026Fix backported to PHP 8.1.34, 8.0.30 and 7.4.33 on Linux.
  13. cPanel docs: about EasyApache 4 (MultiPHP)A cPanel server can assign a different PHP version to each domain.
  14. CISA Known Exploited Vulnerabilities catalog (CSV feed)Both CVEs added 26 October 2026, federal due date 29 October. Checked 4 November 2026.
  15. Regulation (EU) 2016/679 (GDPR), Articles 33 and 34 (EUR-Lex)33(1): controller notifies the authority within 72 hours where feasible. 33(2): a processor notifies the controller without undue delay. 34(1): high-risk breaches are communicated to the people affected.

Facts on this page are dated and point at the primary source next to them. If a vendor status changes after the date shown, the vendor's page wins; tell us at support@run.cloud and we will update it.