PHP2Shell · CVE-2026-109618 and CVE-2026-109619

Is your website exposed to PHP2Shell?

Two PHP flaws disclosed October 21 let anyone take over a web server with a single request, no login. Run a free scan and we'll show you which of your sites announce an affected PHP version, including the ones nobody remembers.

https://

We only read what your servers already tell every visitor (one ordinary page request). We never send attack traffic or "test" payloads. A hidden version isn't proof of a patch, so we say so.

What the free scan checks

  • Every hostname we can find for your domain, from public certificate logs, not just the main site
  • The PHP version each site announces, matched against the fixed releases
  • Distribution builds marked "confirm with your host" instead of a false alarm
  • Sites that use PHP but hide the version, so you know what to ask about

No signup. Results in about 30 seconds.

In plain English

What it is and what to do.

What happened

PHP runs a huge share of the web, including most WordPress sites. On October 21, 2026 the PHP project shipped fixes for two flaws, nicknamed PHP2Shell, that let an attacker run their own code on the server. Attack attempts climbed into the millions within days.

Who is affected

Any server on a PHP version older than 8.5.12, 8.4.27, 8.3.36 or 8.2.35, and anything still on PHP 8.1 or older, which no longer gets official fixes. Linux distributions (Ubuntu, Debian, Red Hat) ship their own patched builds that keep the old version number.

What to do

Update PHP and restart it, on every server, including old marketing sites, staging copies and vendor-run portals. If a site can't be patched today, put a firewall rule in front of it or take it offline until it can. Then stop announcing the PHP version (expose_php = Off).

Keep watch

Next time, hear it from us first.

ExpirySentry watches every certificate, domain and live site you own, alerts the right person before anything lapses, and flags new incidents like this one the day they land. Starter is free for 14 days, no card.

FAQ

Is this a penetration test?

No. It's the same request a browser makes. We read the response headers, never send exploit code, and never log in.

Our site says PHP 8.1.2. Are we vulnerable?

If it's an Ubuntu or Debian build (the version string usually says so), it may already be patched, because distributions don't change the number. Ask whoever runs it to confirm the October PHP security update is installed. A plain "8.1.2" with no distribution tag is end of life and needs an upgrade.

Do you watch for this going forward?

Yes. Monitoring rechecks every live site daily and alerts the named owner the moment a site announces an affected version.

What is a certificate, in plain terms?

A digital ID card for your website, VPN and email servers. It proves to browsers and staff laptops that they're talking to the real you. Every one has an expiry date, and when it passes, browsers show a security warning, remote staff can't connect, and some email stops flowing.

Do you renew the certificates for us?

No, and that's on purpose: we're the independent check on whoever does, whether that's your team, your IT provider or your auto-renewal setup. We find everything, tell the owner early with the exact fix, and keep reminding them until it's renewed. Need hands-on help with a tricky renewal? Talk to us.