PHP2SHELL Four governments took sites offline, Reuters reports

A vulnerability hits, your sites protect themselves

Manicou spots the vulnerability that affects your sites and shields them until the fix.

  • Free up to 50 sites
  • Protection from €1 a month
  • For freelancers, agencies and hosts

Manicou

  • Dashboard
  • Sites1
  • Vulnerabilities2
  • Domains
  • Log
  • Status pages

Settings

  • Alerts
  • Channels
  • Team
  • API
Onlinewww.exemple-boutique.fr

Checked every minute

Check nowPause

Protected, not fixed yet

Open vulnerabilitiesForms closed since 15:42

  • PHP · Remote takeoverRCE via OOM corruption
    CriticalExploited
    Protectedin 8 min
  • PHP · Remote takeoverRCE via stale global state
    CriticalExploited
    Protectedin 8 min
  1. Alerted
  2. Order sent
  3. Protected
  4. Verified
  5. Update started
  6. Fixed

Availability

  • 7 d100%
  • 30 d99.96%
  • 90 d99.98%

Response time

520 ms

24-hour average

Expiry dates

  • Certificateuntil 12 March 2027
  • Domainuntil 14 March 2027

Nearly 200 products watched for vulnerabilities, version by version.

  • PHP
  • WordPress
  • Node.js
  • nginx
  • Apache
  • React
  • Laravel
  • Python
  • PostgreSQL
  • Drupal
  • Next.js
  • Redis
  • OpenSSL
  • Django
  • MongoDB
  • Joomla
  • Ruby
  • MariaDB
  • Symfony
  • PrestaShop
  • Kubernetes
  • Angular
  • .NET
  • Traefik
  • Rails
  • GitLab
  • Ghost
  • Nuxt
  • Elasticsearch
  • Caddy
  • Spring
  • Grafana
  • TYPO3
  • Svelte
  • Tomcat
  • Jenkins
  • Nextcloud
  • Express
  • HAProxy
  • OpenJDK
  • Moodle
  • Flask
  • Keycloak
  • jQuery
  • Bootstrap
  • RabbitMQ
  • Odoo
  • NestJS
  • Prometheus
  • Hugo
  • Discourse
  • Kafka
  • SQLite
  • Jetty
  • phpMyAdmin
  • Go
  • Gitea
  • Helm
  • Mastodon
  • Vault

On 21 October 2026, two flaws threatened 69% of websites whose language is known

PHP runs these sites, according to W3Techs, as of 9 November 2026.

With PHP2SHELL, anyone could take over a PHP site, no password needed. As a precaution, the Dutch, French, Danish and Finnish governments took sites offline.

According to Reuters, 21 October 2026.

101online services reported down or in maintenanceAccording to StatusGator, 22 October 2026 at 00:30 UTC

27 millionPHP web services still vulnerable, more than three weeks after the fixesAccording to Censys, as of 14 November 2026

What eight well-known services did
  • WikipediaSystems taken offline
  • Dropbox SignEmergency maintenance
  • Laravel CloudDeployments paused
  • HostingerNotice posted
  • IONOSNotice posted
  • NamecheapNotice posted
  • KinstaNotice posted
  • CloudwaysNotice posted

According to StatusGator, and Reuters for Wikipedia.

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

  • You have to see the alert and act, day or night
  • Your sites are taken down, or left exposed, until the fix
  • You bring them back online one by one

With Manicou

0 clicks

to protect every affected site

  • Manicou shields your sites for you, even on a Sunday at 3 a.m.
  • Your sites stay browsable, only forms and admin are closed
  • Everything goes back to normal once the fix is installed

In this example, automatic protection is on and acts before PHP, from Cloudflare, nginx or Apache.

And it is no one-off: 50% more vulnerabilities published in the first half of 2026 than a year earlier.

According to Jerry Gamblin, 1 July 2026.

From vulnerability to fix, each step triggers the next

In this example, two sites are shielded 8 min after the alert, before the fix even exists. The average, calculated from our timings, is 10 min.

  • Manicou spots the vulnerabilities that affect your sites
  • It tells each affected site to protect itself
  • It checks from outside that it’s done
  • It returns each site to normal once fixed
How it works

Log

  1. PHP announces two vulnerabilities
  2. Alert, and order sent to the site
  3. Forms close
  4. Protection verified from outside
  5. The update is launched
  6. PHP 8.3.36, back to normal
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

Set up in three steps

  1. 1

    Add your sites

    Manicou detects their software from outside, or from a file you upload. A DNS record proves the domain is yours.

    • www.exemple-boutique.fr
      • WordPress 6.8.6
      • WooCommerce 10.2.1
      • PHP 8.2.29
    • blog.exemple.fr
      • WordPress 6.8.6
      • PHP 8.3.30
      • Apache 2.4.65
    • extranet.exemple.fr
      • Laravel 12.30
      • PHP 8.4.20
      • nginx 1.28.0
  2. 2

    Install your host’s recipe

    The recipe is a few files that apply the protection, installed once. On PHP and WordPress, a folder to copy and one line at the top of index.php, filled in for your site by your dashboard. Without a recipe, a site stays exposed.

    index.phpEffect confirmed
    <?php
    require __DIR__ . '/chargeur.php';
    The recipes for Cloudflare, Vercel, Netlify, nginx, Apache and Node
  3. 3

    Choose what happens

    By severity, just warn, or shield the site.

    • EmailOrder
    • ExploitedRestricted
    • CriticalRestricted
    • HighNone
    • MediumNone
    • LowNone

You decide once, Manicou takes it from there

Manicou never touches your site. It sends a signed order that no one else can send, and only your recipe applies it.

  • When shielded, your pages stay readable and forms close, checkout included
  • No hosting keys, no access to your server
  • Your visitors’ traffic never goes through Manicou
  • You try the protection before you need it
  • Every recipe’s code is public, to read before you install it
www.exemple-boutique.fr/loginRestricted

Exemple Boutique

Exemple Boutique is protecting you.

A security vulnerability affecting many websites is under way.
Some services are suspended until its fix.

To reach us

+33 1 99 00 12 34

[email protected]

Site protected by Manicou

Complete monitoring, on top of vulnerabilities

  • Availability

    Every outage confirmed from a second region, so you are not woken up for nothing.

    30 days99.96%
  • Response time

    Measured on every check, to see a site slow down before it goes down.

    520 ms24-hour average
  • Certificate and domain

    Warned 14, 7 and 3 days before a certificate expires, 30 and 7 days before a domain does.

    • Certificate 12 March 2027in 142 days
    • Domain 14 March 2027in 144 days
  • Alerts

    By email, Slack, Discord, Teams or signed webhook, a single one per vulnerability.

    3 verified channels
  • Status pages

    A public page for your visitors, with no trackers, showing your outages and maintenance.

    Operational
    • ShopOnline
    • BlogOnline
    • ExtranetScheduled maintenance
  • Heartbeats and API

    A scheduled task that stops checking in alerts you, and your sites can also be managed through the API.

    curl -fsS https://app.manicou.dev/b/…
    • Nightly backup heartbeat at 03:00Online

UptimeRobot monitors, Manicou protects too

CriterionUptimeRobotManicou
50 free sites, every 5 minutesyesyes
Alert before the certificate and domain expirepaidfree
Vulnerabilities affecting each of your sites, spotted for younothing like ityes
Your sites protected without you, and verifiednothing like itwith a plan
Price for 10 sites, paid yearly$9 a month€3 a month

Read on UptimeRobot’s pricing page on 14 November 2026. A dash means we found nothing like it there.

Switch from UptimeRobot to Manicou

Monitoring is free, protection starts at €1 a month

Free

€0

no credit card

  • 50 sites, checked every 5 minutes
  • Downtime and vulnerability alerts by email, Slack, Discord, Teams or webhook

Plans

from€1instead of €3per month

billed yearly, excl. tax

  • From 10 to 1,000 sites, every minute
  • Automatic vulnerability response
See pricing
Launch offer

up to −67%

The first 100 customers get their plan at a third of the price, for life, as long as they keep it.

100 spots left

Frequently asked questions

What do I need to install?

A recipe, a few files installed once on your host, Cloudflare, Vercel, Netlify, nginx, Apache, PHP or Node. Your dashboard gives them to you already filled in for your site, and a test checks that it responds.

Do orders still go through during protection?

No. Protection closes forms, checkout included, and keeps pages browsable. That is why you choose, severity by severity, between just being warned and shielding the site.

What if the alert is wrong?

Manicou matches each vulnerability against your sites’ software and versions, and only protects the sites it affects. A vulnerability it cannot match with certainty is flagged for you to check, without closing anything.

Does my site depend on Manicou to work?

No. Your site runs on its own, Manicou only sends it orders. If Manicou stops responding, your site simply keeps the last order it received.

What happens to my site if I stop?

Nothing is deleted. Sites checked every minute go back to every 5 minutes, and those beyond the free 50 are suspended until you come back. None is shielded any more, and you remove the recipe whenever you like.

Why not my firewall or Dependabot?

A firewall filters the attacks it recognizes, and Dependabot proposes updates in your GitHub repository. Manicou does something else, it knows which sites a vulnerability affects and shields them until the fix. It adds to them, it does not replace them.

Monitor your sites for free

Protect them when you’re ready.

Test my site