phpAfterShell (CVE-2026-126714): What Website Owners Should Do Now

phpAfterShell (CVE-2026-126714): What Website Owners Should Do Now

On 19 November 2026, the PHP project released security updates that fix 17 or more vulnerabilities, several rated critical. The headline flaw has a name: phpAfterShell, tracked as CVE-2026-126714 and rated 9.2 (critical).

PHP runs a large share of the web, including WordPress, WooCommerce, Joomla, Drupal and Laravel sites. If your business has a website, there’s a good chance it runs on PHP, so this one is worth ten minutes of your time.

What is phpAfterShell?

phpAfterShell is a flaw in PHP’s built-in session handling, the feature that remembers who a visitor is between page loads.

In simple terms:

  • When the upload progress feature is turned on, PHP can write to a visitor’s session file while it’s still receiving an upload.
  • A carefully timed request can leave that session file partly overwritten.
  • When the site later reads the damaged session, PHP trusts it and rebuilds data from it. In the right conditions, that lets an attacker run their own code on the web server.

The code runs with the permissions of the PHP process. That’s usually enough to change website files, plant malware, steal data from the site’s database or send spam.

It also matters because it bypasses the fix for PHP2Shell, a similar flaw patched in October 2026. Sites that patched last month are still exposed until they install the November update.

How serious is it?

Security researchers rate it critical, and proof-of-concept material is reported to be public. Exploitation isn’t trivial: it needs specific settings, precise timing and repeated attempts. But attackers automate exactly this kind of work, and many sites run with default settings.

The same release also fixes CVE-2026-129289, a critical PHP-FPM flaw that can let unauthenticated attackers run PHP code on some server setups that reuse FastCGI connections.

Even the US National Security Agency felt the impact this week: reports say a multi-day outage of its internal network was linked to how it rolled out updates for these PHP flaws. Patching matters, and so does testing your updates.

Which PHP versions are affected?

According to published advisories, these versions are fixed:

PHP branchFixed in
8.28.2.36
8.38.3.37
8.48.4.28
8.58.5.13

Anything older on those branches is affected. Sites on PHP 8.1 or older are on versions that no longer get regular security fixes, and should move to a supported version as soon as possible.

What to do: website owners

1. Find out which PHP version your site runs

  • WordPress: go to Tools > Site Health > Info > Server. It shows the PHP version.
  • Hosting control panels (hPanel, cPanel, Plesk) usually show it under PHP Configuration or Select PHP version.
  • Or ask your hosting provider or web developer.

2. Get PHP updated

  • Shared and managed hosting: most hosts patch PHP for you, but not always on the same day. Contact support and ask: “Have you applied the 19 November PHP security updates (phpAfterShell, CVE-2026-126714) to my site’s PHP version?”
  • Your own server or VPS: install the updated PHP packages from your distribution or repository, then restart PHP-FPM (or your web server). The fix doesn’t take effect until the PHP processes restart.

3. Update WordPress, plugins and themes

The PHP update fixes PHP itself. While you’re there, update WordPress core, plugins and themes, and remove any you no longer use. Outdated plugins are still the most common way small business sites get hacked.

4. Make sure you have a recent backup

Before changing PHP versions, take a full backup (files and database), and make sure you know how to restore it. A PHP upgrade occasionally breaks an old plugin.

5. Look for signs of compromise

If your site was slow to patch, check for:

  • New administrator accounts you don’t recognise
  • Unknown files in wp-content/uploads (especially .php files)
  • Unexpected redirects, spam pages or warnings from Google Search Console
  • Security plugin alerts

If anything looks wrong, see our guide on what to do in the first minutes after a hack.

What to do: IT teams and developers

  • Patch every PHP installation, including internal tools, intranet apps and old test servers.
  • If you don’t need it, turn off session upload progress (session.upload_progress.enabled = Off in php.ini) as an extra layer of protection.
  • Restart PHP-FPM pools after updating, and confirm the new version with php -v and a phpinfo() check on the web server itself (the command-line version can differ from the one the web server uses).
  • Test updates on a staging copy first where possible, but don’t let testing delay a critical fix for weeks.

Quick checklist

StepDone?
Know which PHP version each website runs
PHP updated to 8.2.36 / 8.3.37 / 8.4.28 / 8.5.13 or later
PHP-FPM or web server restarted
WordPress, plugins and themes updated
Recent backup taken and restore tested
Checked for unknown admin users and files

phpAfterShell is a good reminder that your website is part of your attack surface, even if it’s “just a brochure site”. Make sure someone, whether you, your developer or your host, is responsible for keeping it patched.

Sources: PHP security release (19 November 2026), Wiz, Field Effect and SOC Prime analyses, CNN reporting on the NSA network outage.