21dev
Critical · actively exploited
⸻ PHP2Shell · CVE-2026-109618 & CVE-2026-109619

PHP vulnerability? We close it within 24 hours.

Two critical flaws in the PHP core (CVSS 9.2) let attackers take over your web server without logging in — and they are already being exploited. WordPress, TYPO3, Shopware or custom code: we patch, look for signs of compromise and lock your site down.

Check your website for free

We load your homepage once — like a browser — and read what your server reveals about PHP.

Nothing invasive — just a normal page visit. Our team also receives the result so we can help you.

Safe from PHP 8.5.12 · 8.4.27 · 8.3.36 · 8.2.35

  • Reply in under 1 hour
  • Fixed within 24 hours
  • Emergency fix from €490
  • Senior team, based in Hamburg
⸻ At a glance

What is PHP2Shell?

PHP2Shell is the name for two critical security flaws in the core of PHP, the language that powers WordPress, TYPO3, Joomla, Shopware and a large share of the web. Details leaked early on 20 October 2026; the PHP project shipped fixes on 21 October, and agencies including CISA, CERT-EU and Germany's BSI issued urgent warnings.

Type of flaw
Two use-after-free bugs in the PHP core that allow unauthenticated remote code execution.
Identifiers
CVE-2026-109618 and CVE-2026-109619 (“PHP2Shell”)
Severity
CVSS v4.0: 9.2 out of 10 (critical) · BSI warning level 3 / orange
Affected
Any PHP installation serving web requests: Apache with mod_php, PHP-FPM, php-cgi, FrankenPHP, LiteSpeed. mod_php is considered most exposed.
Fixed in
PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 (since 21 October 2026)
No official fix
PHP 8.1 and older (end of life). Only source patches exist for 7.4, 8.0 and 8.1 — or backports from your Linux distribution.
Exploitation
Attacks have been observed in the wild. The first attempts date back to 17 October — four days before the patches.
Third flaw
CVE-2026-115560 was announced on 23 October. It is considered hard to exploit, can be mitigated through configuration and will be fixed in the next regular PHP release.
⸻ Why it matters now

An update alone is often not enough.

Many site owners assume they're safe because WordPress is up to date or their host will update “at some point”. These four things are almost always missed:

A WordPress update ≠ a PHP update

The flaw lives in PHP itself, not in your CMS. An up-to-date WordPress can still run on unpatched PHP. What matters is the PHP version on your server.

Attacks started before the patch

The first exploitation attempts were seen on 17 October. If you were exposed, you need to check whether someone already got in — a backdoor survives every update.

Credentials may have leaked

CVE-2026-109618 can leak memory from other requests — such as passwords, session tokens or API keys. After patching, credentials should be rotated.

Old PHP versions stay open

PHP 8.1, 8.0 and 7.x get no official release. The only options are a backport, an upgrade — or moving to a modern stack.

⸻ Our services

Three ways out of the PHP hole.

Seal it now, leave PHP for good, or have us look after it — your call. Every package starts with a free, no-obligation first assessment.

Immediate help

Emergency Fix 24h

For everyone who needs to be safe right now — whatever the system.

from€490one-off

  • Reply in under 1 hour, fixed within 24 hours
  • PHP update to a patched version — or a backport for older systems
  • Hardened PHP and server configuration
  • Compromise check: web shells, rogue admin accounts, modified files
  • Rotation of passwords, keys and sessions
  • Short report with findings and clear recommendations
Request emergency fix
Secure for good

Switch to Next.js

Leave PHP behind — move to a fast, modern stack.

from€4,900per project

  • Rebuilt with Next.js & React — no PHP runtime on the server
  • Content and rankings stay: migration incl. 301 redirects
  • Headless CMS — your team keeps editing content
  • Pre-rendered via CDN: noticeably faster, strong Core Web Vitals
  • No more plugin updates or plugin vulnerabilities
  • Your current site stays secured until go-live
Discuss the switch
Fully managed

Managed Security

We keep your website secure. You run your business.

from€149/ month

  • Critical security updates within 24 hours
  • Continuous monitoring of PHP, CMS and plugin vulnerabilities
  • Uptime monitoring with alerts
  • Daily off-site backups
  • Monthly security report
  • Direct line via WhatsApp and phone
Request managed security

All prices are net, plus 19% German VAT where applicable. You get a fixed price after the first assessment — before we start.

⸻ 60-second check

Are you affected?

  • Your site runs on WordPress, WooCommerce, TYPO3, Joomla, Drupal, Shopware, Magento, Contao or custom PHP code (Laravel, Symfony …).
  • Your PHP version is below 8.5.12, 8.4.27, 8.3.36 or 8.2.35 respectively.
  • You are running PHP 8.1 or older.
  • You don't know exactly which PHP version you run or who maintains your server.

How to find your PHP version: in your hosting control panel (often under “PHP settings”) or in WordPress under Tools → Site Health → Info → Server.

If even one of these applies, check your site with our free tool — or just send us the address.

Check automatically now
⸻ How it works

Here's how fast we move.

  1. 01 · Now

    Get in touch

    WhatsApp, call or email. Your website address is all we need to start.

  2. 02 · < 1 hour

    First assessment

    We check your PHP version, hosting and risk — and give you a fixed price.

  3. 03 · < 24 hours

    Secure

    Patch, hardening, compromise check and fresh credentials. We keep your site online wherever possible.

  4. 04 · After

    Report

    You get a plain-language summary and concrete next steps.

⸻ Whatever your site runs on

We help with any PHP system.

From a small WordPress site to a custom-built shop — with any host, on shared hosting, a VPS or your own server.

  • WordPress
  • WooCommerce
  • TYPO3
  • Joomla
  • Drupal
  • Shopware
  • Magento
  • Contao
  • Laravel
  • Symfony
  • CodeIgniter
  • Custom PHP code

We know PHP inside out: many of our own projects run on WordPress and WooCommerce.See our work

⸻ Think long term

Why Next.js instead of PHP?

PHP2Shell isn't the first critical PHP flaw and won't be the last. If you were planning to modernise anyway, this is the best reason yet.

TopicPHP / WordPressNext.js (twentyfirst.dev)
Affected by PHP2ShellYes, unless patchedNo — no PHP runtime
Attack surfacePHP runtime, CMS, theme and plugins on the serverPre-rendered pages, minimal server code
MaintenanceConstant updates for core, theme and often dozens of pluginsA few vetted dependencies
SpeedDepends on plugins, caching and hostingServed from a CDN, very fast load times
SEO & Core Web VitalsAchievable — with effortExcellent out of the box

To be honest: no technology is unbreakable — Next.js has had security flaws too. The difference is a much smaller attack surface. With our managed security service we apply updates within 24 hours.

⸻ FAQ

PHP2Shell: frequently asked questions

What is PHP2Shell?

PHP2Shell refers to two critical security flaws in the PHP core (CVE-2026-109618 and CVE-2026-109619, CVSS v4.0 9.2). They let attackers run code on a web server without logging in. Details leaked early on 20 October 2026, and patches were released on 21 October.

Is my WordPress site affected?

Very likely, if your server hasn't been updated yet. WordPress, TYPO3, Joomla, Shopware and others all run on PHP. What matters isn't your WordPress version but your server's PHP version: PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 or newer are safe.

How do I find out my PHP version?

The quickest way is our free check at the top of this page — if your server reveals its version. Otherwise, look in your hosting control panel (usually under “PHP settings”) or in WordPress under Tools → Site Health → Info → Server. Or just send us your website address.

My host updated PHP — am I safe now?

The update stops new attacks but doesn't undo a break-in that already happened. Because attacks started before the patches, you should have your site checked for backdoors, rogue admin accounts or modified files — and rotate credentials, since CVE-2026-109618 can leak memory contents.

How much does the emergency fix cost?

The emergency fix starts at €490 net. After the free first assessment you get a fixed price before we start. The switch to Next.js starts at €4,900 and managed security at €149 per month.

How fast can you help?

You'll get a reply in under an hour. Securing your site is usually completed within 24 hours of your go-ahead.

I'm on PHP 8.1 or older — what now?

PHP 8.1, 8.0 and 7.x get no official release. Short term, we apply a backport or upgrade you to a supported PHP version and test your site on it. Long term, we recommend an upgrade or a switch to Next.js.

What about the third flaw, CVE-2026-115560?

The PHP Foundation announced a third flaw on 23 October 2026. According to the Foundation it is only exploitable with a very unlikely combination of configuration and application code and can be mitigated through configuration. The fix will ship with the next regular release. Our emergency fix applies the mitigation right away.

Is Next.js secure by default?

No technology is unbreakable. But a Next.js site serves pre-rendered pages and needs no PHP runtime and no plugins, so its attack surface is much smaller. It is not affected by PHP2Shell. With managed security we keep it up to date as well.

What access do you need?

Depending on your setup: your hosting control panel, SSH or SFTP, or an admin login for your CMS. We treat everything confidentially and can sign a GDPR data processing agreement (DPA) on request.

Do you help outside Germany?

Yes. We work fully remotely, in English and German, for clients in Germany, Austria, Switzerland and worldwide.

⸻ Act now

Don't leave the hole open.

Reach us however is fastest for you. Reply in under an hour.

Your direct contactRobin Trepte · Managing Directorrobin@twentyfirst.media