Read them in this order. Each guide stands on its own, and every fact is footnoted to /sources, which gives its primary source and date.
- PHP2Shell for business owners: what happened, am I affected, and what to do now
What happened, whether your site is in scope, who patches it, and what to do this week. - What to ask your host or developer after PHP2Shell: a copy-ready email and checklist
A copy-ready email for your host or developer, what a good answer looks like, and the red flags. - How to prove your server is patched for PHP2Shell, when the version number can’t
Why a version number can’t prove a patch, and the evidence that does, per CVE. - PHP2Shell and cyber insurance: what evidence to keep
The dated evidence to keep for your insurer, and how to describe what you checked. Not legal advice. - PHP 8.2 end of life on December 31, 2026: a practical checklist
What end of life means, which version to move to, and the upgrade steps. - Moving WordPress from PHP 7.4 to 8.4: what breaks and how to check
What tends to break between PHP 7.4 and 8.4 on WordPress, and how to check before you switch. - The agency guide to PHP2Shell: triaging dozens of client sites, with go/no-go decisions
Go/no-go calls across many client sites, with client updates and evidence. - Frequently asked questions: PHP2Shell, proving a patch and PHP 8.2 end of life
Short, sourced answers to common questions.
Also useful
- PHP2Shell, explained: the full explainer, with the email to send your host.
- The sample evidence report: what a Patch Verification delivers.
- Services and prices, including when you don’t need us at all.