GoodJava Software Solutions Get help
Security advisory · Updated October 27, 2026

PHP2Shell: what happened and what to do next

Two critical flaws in PHP, the software behind most websites, were fixed on October 21, 2026. Here is what happened, who is at risk, and how to get it handled, with your IT provider or with us.

What happened

On October 21, 2026, the PHP project released fixes for two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, now known as PHP2Shell. Both are rated 9.2 out of 10.

PHP is the software that runs on the web server behind most websites, including every WordPress, Drupal and Joomla site. These flaws let an attacker run their own code on that server with a single web request and no login. The problem is in PHP itself, before your website's code ever runs, so a well-built site is just as exposed as a basic one.

Details leaked before the fix was ready, and attack attempts were reported before the patch shipped. Government security agencies, including CISA, told organizations to patch immediately.

The same week, Node.js fixed a related flaw nicknamed Node2Shell (CVE-2026-111497) in the Brotli decoder it bundles. It can allow remote code execution in web apps built on Node.js.

Updating WordPress or your plugins does not fix this. The fix is in the server software underneath your site.

Who's vulnerable

Any business with a website, portal or web app should check. Where your site runs matters more than how it was built.

Must upgrade
PHP 8.1 or older, or Node.js 20, 23 or 25
These versions will never get an official patch. CISA advises taking PHP systems on 8.1 or older offline until they are upgraded.
Likely at risk
Servers you or a developer manage
Websites, customer portals, logins and online stores on a VPS, cloud server or office server. Apps in Docker containers or CI pipelines built before October 21 need rebuilding. Software from a vendor: ask the vendor for a written statement.
Ask your host
Shared or managed hosting
Your host patches PHP for you, and most major hosts say they already have. Get the patch date in writing, along with the PHP version your site uses.
Not affected
Wix, Squarespace and Shopify
These platforms run the servers themselves. There is nothing for you to patch.

What's next

  1. List what you run

    Your website, portals and web apps, where each is hosted, and who has the logins.

  2. Ask the right people

    Your host, your IT provider and any software vendor. Ask each to confirm in writing that what they run for you is patched.

  3. Patch or upgrade

    Install the fixed version and restart PHP or Node.js. On an end-of-life version, plan the upgrade now.

  4. Check for signs of attack

    Patching closes the door but won't remove anything already inside. Look for unknown admin users, unfamiliar files or unusual server load since mid-October.

Need a hand? Start with who you already trust.

Patching a server is routine. Finding old versions hiding in custom apps, containers and build pipelines, and upgrading the ones with no fix, is developer work. That's where GoodJava comes in.

Have an IT provider or MSP?

Reach out to them first. We work alongside IT teams on the developer side, and your provider stays your point of contact. They can bring us in, or you can.

No IT provider?

Contact us directly. We'll look at your sites and tell you plainly whether you need to do anything, and quote any fix before work starts.

Are you an IT provider?

We partner with MSPs to check client lists and handle the app work behind you. You keep the client.