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.fr
    Protectedin 8 min
  • www.exemple-boutique.fr
    Protectedin 8 min
  • extranet.exemple.fr
    Exposed
  1. Alerted
  2. Order sent
  3. Protected
  4. Verified
  5. Update started
  6. Fixed
Follow the update
  1. Before
    InventoryPHP 8.3.30, read on GitHub.
  2. 15:34
    WatchPHP announces two vulnerabilities.
  3. 15:41
    DecideCritical, and this version is affected.
  4. 15:41
    AlertAlert by email, Slack and webhook, and order sent to the site.
  5. 15:42
    ProtectThe site’s recipe applies the order, and forms close.
  6. 15:43
    VerifyProtection verified from outside.
  7. 16:05
    FixThe fix is out: the update is launched.
  8. 17:41
    LiftPHP 8.3.36, back to normal.
  9. Result
    MeasureProtected 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.