php2shell: Two Critical PHP RCEs Were Patched Today — Is Your App Still Exposed?

Check your own app — free, in about a minute.

php2shell exposure is one of the mini-scan's own checks: it flags exposed PHP version information and vulnerable WordPress core, plugin and theme versions on your live site — the same disclosure an attacker reads first. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

php2shell: Two Critical PHP RCEs Were Patched Today — Is Your App Still Exposed?

If your app runs on PHP — a Laravel or WordPress backend, a PHP API behind your shiny AI-built frontend, the stack your hosting plan came with — today is a drop-everything day. Two critical vulnerabilities in PHP itself were patched this morning, they're already being exploited, and the fix takes most people less time than reading this article. Here's what happened, how to check your own version in about 60 seconds, and what to do if you're exposed.

What Happened

Security researchers dubbed it "php2shell": two separate flaws in PHP core, tracked as CVE-2026-109618 and CVE-2026-109619. Both are unauthenticated remote code execution vulnerabilities — an attacker needs no account, no password, and no prior access. Each carries a CVSS v4 score of 9.2, about as severe as a web vulnerability gets. A single specially crafted request to a vulnerable server can be enough to run code on it.

The timeline is why this is urgent:

This is not a bug in one PHP framework or one plugin. It's in PHP itself, and it affects every common way of serving PHP on the web: PHP-FPM, mod_php, CGI, FrankenPHP, and LiteSpeed setups are all in scope. If your app serves PHP, assume you're affected until you've checked your version.

The Fixed Versions

PHP patched the four supported branches. Your version is safe from php2shell only if it's at or above the fixed release for your branch:

Your PHP branch You're patched at
8.2.x 8.2.35 or later
8.3.x 8.3.36 or later
8.4.x 8.4.27 or later
8.5.x 8.5.12 or later

Anything below the number for your branch is exposed — including versions that were fully patched yesterday. This flaw is new; last week's update doesn't cover it.

The EOL Problem: PHP 8.1 and Older Get No Fix

Here's the part that will bite a lot of founders: PHP 5.x through 8.1 are end-of-life, and no patch is coming for them. There is no "update" that fixes php2shell on those branches. The only fix is to move to a supported branch (8.2 or newer, then patch to the version above).

A lot of long-running WordPress sites, older Laravel apps, and "it works, don't touch it" hosting plans are sitting on 8.0 or 8.1. If that's you, treat this as the forcing function: schedule the upgrade now, and until it's done, understand that your server is exposed to a known, actively exploited, unauthenticated RCE. A web application firewall rule may blunt some attack traffic, but it's a seatbelt, not a fix — the only real remediation is a supported, patched PHP.

Check Your Version in 60 Seconds

You don't need to guess. One of these three will tell you exactly what you're running:

1. If you can open a terminal on your server:

php -v

The first line prints your exact version. Compare it against the table above.

2. In your hosting panel: cPanel, Plesk, and most managed hosts show the PHP version (and let you change it) under a setting named something like "PHP Selector," "MultiPHP Manager," or "PHP Settings." On managed WordPress hosting, it's usually in your site's dashboard or settings page. If you find the setting, you can check and fix in the same place — bump to the newest version your host offers on a supported branch.

3. From the outside, the way an attacker sees it: many PHP servers announce their version to every visitor in an X-Powered-By header:

curl -sI https://yourdomain.com | grep -i x-powered-by

If that prints something like PHP/8.3.10, you have your answer from the parking lot, no login required. Our free mini-scan reads exactly this disclosure and now flags PHP versions known to be vulnerable to php2shell — paste your URL and it takes about a minute.

If the header is missing, that's "unconfirmed," not "safe." Plenty of well-configured servers strip the version header (a good practice — it's why our own scan reports flag version disclosure). A stripped header means an outsider can't see your version; it says nothing about whether you're patched. Check with method 1 or 2, and patch anyway. The attackers aren't relying on your header — they're just trying the attack, and an unpatched server answers.

What To Do If You're Exposed

  1. Update PHP now to the fixed version for your branch (table above), or, on an EOL branch, upgrade to a supported one. On most managed hosting this is a settings change plus a restart; on your own server it's your package manager or container image.
  2. Restart the PHP service (FPM, your app server, or your container) so the patched version is actually the one serving traffic.
  3. Re-check from the outside — re-run the header check or mini-scan and confirm.
  4. Test your app after the bump. Minor PHP version updates are designed to be low-risk, but branch jumps (8.1 → 8.3, say) can surface deprecations in old code. Click through your critical flows, check your error logs, and keep the old setup restorable until you've verified.
  5. Then think about how long you were exposed. The details leaked yesterday and exploitation is confirmed, so the window is short — but if your server was reachable and unpatched, it's worth a pass over your access logs and a check for accounts or files you don't recognize. Our guide to checking whether your web app is hacked walks through the signs.

Once you're patched, do the thing that makes the next emergency boring: note where your PHP version setting lives, and turn on whatever update notifications your host offers. PHP version drift is invisible until the day it's a headline.

WordPress? Also Check This Plugin

WordPress sites face a second, independent emergency this month: the Bricksforge plugin has its own critical flaw, CVE-2026-85097 — a CVSS 10.0 unauthenticated file-upload vulnerability that also leads to remote code execution, exploited in the wild since October 7. It's fixed in Bricksforge 3.1.8.10. If your site uses Bricksforge, update it today regardless of your PHP version: this one lives in the plugin, so patching PHP doesn't touch it. Two different holes, two different fixes — you need both.

The Short Version

Run the free mini-scan at preshipit.com/free-scan — paste your URL and see what your server discloses to strangers, including a vulnerable PHP version if it's announcing one. If you want the full picture before you ship (or after today's patch), the full scan is $29, one-time.

The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.

New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.

Check your own app — free, in about a minute.

php2shell exposure is one of the mini-scan's own checks: it flags exposed PHP version information and vulnerable WordPress core, plugin and theme versions on your live site — the same disclosure an attacker reads first. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report