Try free for 14 days

Critical PHP flaw PHP2Shell · 21 Oct 2026

Which PHP version is your website running?

The critical PHP vulnerability PHP2Shell has been public since 21 October 2026. This check shows in seconds which PHP version your website reveals, whether it still gets updates and what you should do now.

Check PHP

  • Free, no sign-up
  • Public pages only, no attacks
  • Honest about what cannot be seen from outside
  • PHP
  • X-Powered-By
  • WordPress
  • Plugins
  • PHP2Shell

How to check the version yourself

These ways show the PHP version your website really uses.

How to check the version yourself

PHP2Shell

What happened on 21 October 2026

The PHP project closed two critical flaws in the PHP core: CVE-2026-109618 and CVE-2026-109619, severity CVSS 9.2 out of 10. Security firms are already reporting attacks.

What happens

Crafted web requests can run foreign code on the web server without logging in. An attacker can then change your website, read data or send emails.

Who is affected

Every PHP installation that answers web requests: WordPress, Joomla, online shops, contact forms and custom PHP applications.

What to do now

Update PHP to 8.5.12, 8.4.27, 8.3.36 or 8.2.35 and have PHP restarted. On PHP 8.1 or older, move to a supported branch.

Source: php.net, security advisory of 21 Oct 2026

Transparency

What the check does and does not do

We only check what any visitor of your website can see, and fetch at most 14 addresses.

What we check

  1. Home page headers“X-Powered-By” and “Server” often reveal the PHP version, for example PHP/8.3.12.
  2. Pages without cacheIf a cache swallows the header, we check the home page with a random parameter, a missing page (404) and the www address.
  3. WordPress and other systemsWe recognise WordPress, Drupal, Joomla, TYPO3, shops and other PHP systems by typical traces. For WordPress also the login page, API and feed.
  4. Minimum version from pluginsPlugins and themes linked from your home page state “Requires PHP”. That gives a lower bound, such as “at least PHP 7.4”.
  5. Support and PHP2ShellWe compare the number with the life cycle published by php.net and the fixes of 21 Oct 2026.

What we deliberately do not do

  • No logins, no forms, no passwords
  • No attacks and no deliberately triggered errors
  • No guessing of paths such as phpinfo.php or admin pages
  • No third-party or search engine data
  • Your robots.txt is respected

Why the result is not binding

The check only sees what your server reveals voluntarily. Well-configured servers hide the PHP version. Then we show “not visible”, even though PHP is running.

A visible number can mislead: it may come from a proxy, be deliberately wrong or come from a Linux distribution such as Ubuntu or Debian that installs fixes without a new number.

Only what your hosting panel or WordPress shows under “Site Health” is binding. Use the check as a hint, not as proof.

PHP versions and their support

As of 21 Oct 2026. After end of life there are no more security updates.

BranchStatusActive support untilSecurity updates untilPHP2Shell fixed from
PHP 8.5Active31 Dec 202731 Dec 20298.5.12
PHP 8.4Active31 Dec 202631 Dec 20288.4.27
PHP 8.3Security only31 Dec 202531 Dec 20278.3.36
PHP 8.2Security only31 Dec 202431 Dec 20268.2.35
PHP 8.1End of life25 Nov 202331 Dec 2025no official update
PHP 8.0End of life26 Nov 202226 Nov 2023no official update
PHP 7.4End of life28 Nov 202128 Nov 2022no official update

Source: php.net (Supported Versions, Unsupported Branches, security advisory of 21 Oct 2026)

Know for sure

How to check the version yourself

These ways show the PHP version your website really uses.

  1. WordPress

    Tools → Site Health → Info → Server. It shows the PHP version and extensions.

  2. Hosting panel

    In your provider’s panel (e.g. cPanel or Plesk), look at the PHP version of this very website, not just the server default.

  3. Ask your provider

    Ask specifically: “Is the PHP fix of 21 Oct 2026 (CVE-2026-109618 and -109619) installed on our website?”

  4. Hide the version

    With expose_php = Off the number disappears from the headers. It closes no flaw, but makes targeted attacks harder.

Step 2: email protection

Hijacked web servers send phishing in your name

Whoever takes over your web server can send emails with your domain as the sender. DMARC, SPF and DKIM make sure such forgeries are rejected. Check your domain for free.

Questions about the PHP check

Is the PHP check really free?

Yes, no sign-up and no credit card. We only fetch public pages of your website, just like a normal visitor.

Why does the check say “version not visible”?

Many hosting providers hide the PHP version, and that is a good thing. The check then shows whether PHP is running and, for WordPress, which minimum version is needed. Your hosting panel shows the exact version.

Is my website safe if the check reports “fix included”?

Not necessarily. The check only rates the visible PHP version. Plugins, themes, passwords and other software can have their own flaws.

What is PHP2Shell?

Two critical flaws in the PHP core (CVE-2026-109618 and CVE-2026-109619), fixed on 21 Oct 2026 in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Attackers can run code on the web server without logging in.

May I check other people’s websites?

Only check websites you own or are responsible for. The check only fetches public pages, respects robots.txt and is limited against mass requests.

What does PHP have to do with email security?

A hijacked web server is often abused for phishing, with your domain as the sender. DMARC, SPF and DKIM stop such emails from reaching your customers. That is exactly what DomainRadar monitors.

Pricing

One plan for SMEs

CHF 19 per domain per month, any number of domains, all features included, with 1 month free on the yearly plan.

All prices in CHF are final prices. Not registered for VAT, no VAT is charged. Monthly plan in arrears, yearly plan once in advance (1 month free). Every registered domain counts, including parked domains that send no email.

Once you order, you pay by invoice via bexio, payable within 20 days.

Not the right fit if you want a spam filter for your mailbox: DomainRadar protects your domain as a sender and does not filter incoming mail.

Now 14 days free

Protect your domain

Write to us – we show you DomainRadar with example data and work out with you which plan fits.

Or directly by email: info@domainradar.ch

  • No commitment
  • No credit card
  • Ends on its own after 14 days
Try free for 14 days