
Check your PHP
Status at
PHP2Shell is the name for two critical flaws in PHP itself, CVE-2026-109618 and CVE-2026-109619.
PHP released fixes on 21 Oct 2026. Its advisory says the releases fix two critical vulnerabilities that can allow unauthenticated remote code execution
. Update to the version on your branch's ticket below, or newer. PHP 8.1 and older get no official release; PHP published source patches for 7.4, 8.0 and 8.1, and some vendors ship backports.
Exploitation reported. Amazon says its MadPot honeypots recorded an exploitation attempt on 17 October, four days before disclosure, and more attempts on 21 October from what looked like several actors. watchTowr says it has observed exploitation in the wild since 21 October, on its honeypot network. CISA added both CVEs to its Known Exploited Vulnerabilities catalog on 26 Oct 2026.
Antonio Firmiano, CEO · Last updated
PHP versions and the fix
As of
Support and end-of-life dates:PHP 8.5PHP 8.4PHP 8.3PHP 8.2PHP 8.1All versions
| PHP | Affected | Fixed in |
|---|---|---|
| 8.5 | 8.5.11 and older | 8.5.12 |
| 8.4 | 8.4.26 and older | 8.4.27 |
| 8.3 | 8.3.35 and older | 8.3.36 |
| 8.2 | 8.2.34 and older | 8.2.35 |
| 8.1 and older | 8.1.34 (last release) | No official release |
Source: PHP's advisory and releases feed. Also as versions.json.
What to do
Docker
PHP lives in the image. The official php and wordpress images have been rebuilt with the fixed PHP:
| PHP inside | Rebuilt |
|---|---|
| 8.5.12 | 21–22 Oct |
| 8.4.27 | 21–22 Oct |
| 8.3.36 | 21–22 Oct |
| 8.2.35 | 21–22 Oct |
Tags that name a branch, such as wordpress:php8.3-fpm, php:8.3-apache or wordpress:latest, now have the fixed PHP. Pull, restart, and check the version:
docker compose pull wordpressdocker compose up -d wordpressdocker compose exec wordpress php -vSome tags never move: a full PHP version such as php:8.3.12-fpm, a digest pin, or an older WordPress release such as wordpress:6.8-php8.3-fpm. Tags for PHP 8.1 and older aren't rebuilt either: the 8.1, 8.0 and 7.4 images still ship PHP 8.1.34, 8.0.30 and 7.4.33. Change the tag to one that names a supported branch, then pull. With your own Dockerfile, rebuild from the new base image:
docker compose build --pulldocker compose up -dChecked on Docker Hub on 30 Oct 2026. The riscv64 builds of the Alpine wordpress images still had the old PHP.
Updating WordPress or plugins from the dashboard does not update PHP.
Shared hosting
Ask your host:
Has PHP on my plan been updated for CVE-2026-109618 and CVE-2026-109619?In cPanel, MultiPHP Manager shows the PHP version for each site.
Linux server
Install your distribution's PHP security update, restart PHP-FPM or Apache, then run php -v and check again.
php -vUbuntu, Debian, CloudLinux and other distributions often patch PHP without changing the version number. Their security notice for CVE-2026-109618 and CVE-2026-109619 is the answer for a distribution build.
How this check works
- We check versions. The result says whether your PHP is affected by version. We don't try to trigger the flaws, because anything that proves they fire is an attack.
- Paste mode runs in your browser. What you paste never leaves it.
- Site mode makes one ordinary request to your site, the same as a browser visiting your homepage. It reads the
X-Powered-Byheader your server already sends. PHP sends that header by default, and the official WordPress images leave it on. - We never send attack traffic or exploit code.
- When a site hides its version, or the version comes from a distribution package, we say we can't tell and give you the command to run on the server.
Questions
What is PHP2Shell?
The name given to two critical flaws in PHP itself, CVE-2026-109618 and CVE-2026-109619. PHP rates both 9.2 out of 10 (CVSS v4.0) and released fixes on 21 Oct 2026.
Is PHP2Shell being exploited?
Exploitation is reported. Amazon says its MadPot honeypots recorded an exploitation attempt on 17 October, four days before disclosure, and more attempts on 21 October from what looked like several actors. watchTowr says it has observed exploitation in the wild since 21 October, on its honeypot network. CISA added both CVEs to its Known Exploited Vulnerabilities catalog on 26 Oct 2026. Update PHP now.
Does updating WordPress fix it?
No. The flaws are in PHP, the language WordPress runs on. Updating WordPress, plugins or themes doesn't change your PHP version. Your host, or whoever runs your server or containers, has to update PHP.
My site runs in Docker. Am I affected?
It depends on the PHP version inside your WordPress or PHP image. Paste your compose file above and we'll tell you which container has PHP and whether pulling the image is enough.
Which PHP versions are affected?
See the table at the top of this page. It lists each supported branch and the release that fixes it, copied from PHP's advisory.
Will PHP 7.4 or 8.1 get a fix?
PHP released no update for 8.1 and older. Its security team published minimal source patches for 7.4, 8.0 and 8.1 for people who build PHP themselves, and some Linux distributions and LTS vendors ship backported fixes, so ask your host or vendor. Otherwise move to 8.2 or newer; 8.2 gets security fixes only until 31 December 2026.
Can I protect a server I can't update today?
Only an update fixes it. PHP's advisory lists measures that reduce specific attack paths, such as setting session.upload_progress.enabled=0 in php.ini and restarting every worker, and lowering post_max_size. PHP says these do not make an installation safe.
Is this the same as wp2shell?
No. wp2shell was a pair of flaws in WordPress itself (CVE-2026-63030 and CVE-2026-60137), made public on 17 July 2026. PHP2Shell is in PHP. Fixing one doesn't fix the other.
Does this check attack my site?
No. We make one ordinary request, the same as a browser visiting your homepage, and read the version your server already reports. We never send exploit code. What you paste is read in your browser and never sent anywhere.
Timeline (UTC)
- Amazon's MadPot honeypots record a PHP2Shell exploitation attempt, four days before disclosure. Amazon reported it on 21 October.
- PHP posts an advance notice: two critical flaws, CVSS v4.0 9.2, fix on 21 Oct at 14:00 UTC.
- A post reports two upcoming PHP remote code execution disclosures. Details leak early.
- watchTowr reports exploitation in the wild, seen on its honeypot network.
- PHP releases the fixes: 8.5.12, 8.4.27, 8.3.36, 8.2.35.
- The official php and wordpress images on Docker Hub ship the fixed PHP.
- CISA adds both CVEs to its Known Exploited Vulnerabilities catalog.
Sources
- PHP: Security advisory, critical remote code execution vulnerabilities, update now (21 Oct 2026)
- PHP: GHSA-w8hw-w9fx-j79w (CVE-2026-109618)
- PHP: GHSA-6wmf-4rv5-p3rp (CVE-2026-109619)
- PHP: ChangeLog for 8.x
- PHP: Upcoming Critical PHP Security Release (20 Oct 2026)
- PHP: Supported versions
- watchTowr: PHP2Shell FAQ (23 Oct 2026)
- AWS Security Blog: Amazon threat intelligence identifies PHP2Shell exploitation prior to public disclosure in MadPot (21 Oct 2026)
- CISA: Known Exploited Vulnerabilities catalog
- Docker Hub: php image tags (30 Oct 2026)
- Docker Hub: wordpress image tags (30 Oct 2026)
- PHP: releases feed (JSON)
- Huntress: php2shell, leaked critical PHP vulnerabilities
- Sansec: Critical PHP RCE, CVE-2026-109618 and CVE-2026-109619
- CloudLinux: package availability for CVE-2026-109618 and CVE-2026-109619
- docker-library/wordpress: the php8.3 fpm Dockerfile
- php-src: php.ini-production (expose_php = On)
- nginx: fastcgi_hide_header
- Eye Security: wp2shell defender's guide
Last updated . Found a mistake? Email hello@arvion.ai and we'll correct it.