A critical threat.
A narrow window.
On Tuesday 20 October 2026, the PHP security team gave advance warning of two critical vulnerabilities: CVE-2026-109618 and CVE-2026-109619, collectively known as PHP2Shell. These flaws could allow an attacker to run code on an affected web server without needing a login.
PHP powers widely used platforms including WordPress and WooCommerce. A vulnerability in PHP itself can affect many websites at once, even when their own application code is up to date.
With working exploits becoming public, organisations faced an urgent response. The UK’s National Cyber Security Centre urged organisations to identify affected systems, apply updates and assess for compromise. Its guidance also covered temporary mitigations and taking systems offline where those measures could not be applied promptly.
Reduce the risk while waiting for the fix. Then patch, verify and keep the client informed throughout.
Five stages.
One accountable team.
- Identify & communicate
Early warning
We picked up the advisory as soon as it was published and raised a P1 critical incident. Within hours, the client received an early warning explaining the risk to their business and the work already under way.
- Clear, plain-English communication from the outset.
- An explanation of what would happen next, without jargon or unnecessary alarm.
- Protect & monitor
Reducing exposure before the fix
With no patch available yet, we focused on reducing exposure to known attack patterns and watching for suspicious activity.
- Deployed updated detection and blocking rules through our Active Threat Protection platform across managed servers.
- Cloudflare’s automatically deployed PHP2Shell firewall protections provided an additional layer of defence for sites using its web application firewall.
- Applied interim hardening measures recommended by the PHP security team.
- Monitored systems around the clock for signs of exploitation.
These measures reduced exposure while we waited. Updating PHP remained the only complete fix.
- Investigate & assess
Checking for signs of compromise
As technical details became public, we used them to review logs and activity across managed servers for signs of attempted or successful exploitation.
- No indicators of compromise were identified in the logs and activity reviewed.
- Plan & authorise
An agreed emergency change
Once the release schedule was confirmed, the client received an action plan setting out what would be patched, the expected impact and how we would verify the work.
- Raised and approved the work as an emergency change.
- Prepared to begin as soon as the fixes became available, rather than waiting for a routine maintenance window.
- Remediate & confirm
Patch, restart, verify
PHP released the fixes on Wednesday 21 October 2026. We began rolling them out immediately, patching 48 servers across our client base in around five hours.
- Restarted each affected service individually, keeping disruption to a few seconds per service and avoiding server reboots.
- Checked every site and service after patching and confirmed health through our monitoring.
- Closed the emergency change with a full record of the work, timings and verification results, available to the client through their portal.
Systems patched.
Clients kept informed.
Action before the patch
Layered mitigations and monitoring were put in place while the security updates were being prepared.
No indicators of compromise found
Our review of logs and activity found no evidence of successful exploitation.
No server reboots or unplanned downtime
Brief, controlled service restarts limited disruption to a few seconds per service.
Clear communication from start to finish
The client received early warning, an action plan and a documented completion record, without needing to chase for updates.
More than
applying a patch.
The update is only one part of the job. Knowing what is coming, reducing exposure while a fix is prepared, checking for signs of compromise and verifying systems afterwards all matter.
For the client, that means a provider who takes ownership of the problem and explains what is happening, from the first advisory to the final checks.
Technical background
For details of the vulnerabilities and official remediation guidance:
PHP security release and advance notice NCSC: Critical security issue affecting PHP Cloudflare: Automatically deployed PHP2Shell protections