How it works
Example: PHP2SHELL, 21 October 2026, on blog.exemple.fr.
CriticalExploited
PHP · Remote takeover
RCE via OOM corruption · published at 15:34 · Fix published
- blog.exemple.frProtectedin 8 min
- www.exemple-boutique.frProtectedin 8 min
- extranet.exemple.frExposed
- Alerted
- Order sent
- Protected
- Verified
- Update started
- Fixed
- BeforeInventoryPHP 8.3.30, read on GitHub.
- 15:34WatchPHP announces two vulnerabilities.
- 15:41DecideCritical, and this version is affected.
- 15:41AlertAlert by email, Slack and webhook, and order sent to the site.
- 15:42ProtectThe site’s recipe applies the order, and forms close.
- 15:43VerifyProtection verified from outside.
- 16:05FixThe fix is out: the update is launched.
- 17:41LiftPHP 8.3.36, back to normal.
- ResultMeasureProtected in 8 min, fixed in 2 h.
And for twenty sites
You run 20 PHP sites, yours or your clients’. The alert came on a Wednesday afternoon. The next one may come on a Sunday at 3 a.m.
Without Manicou
20 clicks
to take your sites down one by one, or they stay exposed
With Manicou
0 clicks
to protect every affected site
On 22 October at 00:30 UTC, StatusGator counted 101 of the 213 services citing PHP as down or in maintenance. With Manicou, automatic protection is on, and the recipe is installed on Cloudflare, nginx or Apache, so it acts before PHP, on every site.