Skip to content
Cisent Message us on WhatsAppMessage us

Blog & news

Threat researchCisent

PHP rushed out patches for two critical flaws that let attackers take over a server without a password

The PHP team and the European agency CERT-EU urge updating now: WordPress, Drupal, Joomla and Magento run on PHP, and some governments took services offline while they patched.

On October 21, 2026, the PHP team released emergency versions for two critical flaws, CVE-2026-109618 and CVE-2026-109619. Both score 9.2 out of 10 and allow code to run on the server without logging in.1 WordPress, Drupal, Joomla and Magento run on PHP.2

What happened

Both flaws are in how PHP handles memory between one request and the next. In one, running out of memory in the middle of a request leaves half-prepared data, and the cleanup that follows treats it as valid. In the other, an internal state outlives the request that created it, and the next request uses it before it is reset.1

They affect every PHP installation that serves the web: PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. The PHP team considers mod_php the most exposed, because there it has a demonstrated attack that runs before any application code. The fixed versions are PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35; PHP 8.1 and older no longer receive updates from the project.1

CERT-EU, the cybersecurity agency of the European institutions, called for patching immediately and, where that isn’t possible, isolating exposed systems from the internet until they are fixed. According to its advisory, the technical details are already public and proof-of-concept code has begun to circulate, which makes it more likely that the flaws are already being exploited.3

Some public bodies in the Netherlands and Finland suspended services while they patched, and the Dutch national cybersecurity agency took its own website offline.2 Cloudflare put protections in its web application firewall before the flaws were disclosed,4 but the PHP team is clear: there is no complete mitigation, and updating is the only safe choice.1

Why it matters

Updating WordPress or its plugins doesn’t update PHP. The PHP version is handled by the server or the hosting provider, so the first question is who maintains it. And the problem doesn’t stop at well-known sites: Huntress warned that it reaches shared hosting, admin panels and applications that don’t say they use PHP.2

Where Cisent comes in

An unpatched PHP on a server nobody checks is the kind of gap worth finding before an attacker does.

Sentinel Red Team attacks the organization’s systems with its authorization and within the scope it defines, to find the gaps before an attacker does: the admin panel exposed on a server nobody watches, the service published by mistake, the insecure configuration. It’s ongoing testing, not one audit a year, and every new attack pattern helps train the defense.

Explore Sentinel Red Team

Sources

  1. PHP security team, security releases PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, with advisories GHSA-w8hw-w9fx-j79w (CVE-2026-109618) and GHSA-6wmf-4rv5-p3rp (CVE-2026-109619), October 21, 2026. https://www.php.net/archive/2026.php↩︎

  2. La Tercera, “Alerta mundial por fallas de seguridad en PHP obliga a desconectar sitios web de gobiernos europeos” (in Spanish), October 21, 2026, citing Reuters, Huntress and Wordfence. https://www.latercera.com/tecnologia/noticia/alerta-mundial-fallas-seguridad-php-wordpress/↩︎

  3. CERT-EU, “Security Advisory 2026-018: Critical Vulnerabilities in PHP”, October 21, 2026. https://cert.europa.eu/publications/security-advisories/2026-018/↩︎

  4. Cloudflare, “Cloudflare deploys protections against php2shell vulnerability”, October 21, 2026. https://blog.cloudflare.com/php-vulnerabilities-waf-protection/↩︎