The php2shell vulnerability: how to check and fix your PHP site
Two critical PHP flaws fixed on October 21, 2026 are now on CISA's exploited list. Here's how to check your site, get it patched and look for signs of a break-in.
PHP 8.2 stops getting security fixes on December 31, 2026. Here's what that means for your site, which version to pick and a week-by-week plan to switch in time.
PHP 8.2 end of life is December 31, 2026. After that date, the PHP project stops releasing security fixes for the 8.2 branch, so any new flaw found in it stays open unless your host or a paid vendor patches it. Your website won't switch off on January 1, but it will run on software the PHP project no longer maintains.
The fix is to move to a supported version before then: PHP 8.4 for most WordPress sites, 8.3 if a key plugin isn't ready, or 8.5 if everything you run supports it. You have about 9 weeks, which is enough time to test properly if you start this week.
PHP is the programming language that runs WordPress, WooCommerce and Laravel, and each version has a fixed lifespan. php.net's supported versions page explains that each branch is fully supported for 2 years from its release, then gets 2 more years of fixes for critical security issues only. After that it reaches end of life, and php.net says users "should upgrade as soon as possible, as they may be exposed to unpatched security vulnerabilities."
Plenty of sites are in this spot. W3Techs data from October 27, 2026 shows 8.2 on 27.4% of websites that use PHP 8, second only to 8.3.
These are the PHP supported versions as listed on php.net today:
| Version | Released | Active support until | Security fixes until |
|---|---|---|---|
| PHP 8.2 | Dec 8, 2022 | Dec 31, 2024 (ended) | Dec 31, 2026 |
| PHP 8.3 | Nov 23, 2023 | Dec 31, 2025 (ended) | Dec 31, 2027 |
| PHP 8.4 | Nov 21, 2024 | Dec 31, 2026 | Dec 31, 2028 |
| PHP 8.5 | Nov 20, 2025 | Dec 31, 2027 | Dec 31, 2029 |
| PHP 8.6 | Scheduled Nov 19, 2026 | Not listed yet | Not listed yet |
The PHP 8.6 release date is November 19, 2026, according to the PHP 8.6 release schedule. php.net released the fourth release candidate on October 21 and asks people not to use it in production. Its support dates aren't on php.net's table yet.
PHP 8.1, for comparison, reached end of life on December 31, 2025, according to php.net's unsupported branches page. That date matters for the next section.
Send your website and we will record a free 2 minute video showing the 3 fixes we would make first.
On October 21, 2026, PHP fixed the php2shell vulnerability, 2 critical flaws that can let an attacker run code on a web server without logging in. How that release played out shows exactly what end of life means:
From January 1, 2027, PHP 8.2 is where 8.1 was this October. If a bug of that size turns up next year, no 8.2 release is coming.
Before you plan the upgrade, make sure your 8.2 site has the php2shell fix today: 8.2.35, or a patched build your host confirms in writing.
Here's what the official requirements say:
How to choose the best PHP version for WordPress and your plugins:
Going from 8.2 to 8.4 skips a version, and each PHP release removes or changes some older features, as php.net's migration guide for 8.4 shows. That's why old, unmaintained plugins are the usual source of trouble, and why the plan below starts with testing.
There are 9 weeks between now and the deadline. This plan leaves room for testing, the holidays and a buffer week.
| Week | Dates | What to do |
|---|---|---|
| 1 | Oct 27 to Nov 1 | Confirm the php2shell fix. Take a full backup. List every site and copy on your account with its PHP version, plugins and theme. |
| 2 | Nov 2 to 8 | Check each plugin and theme: when was it last updated, and does the developer mention PHP 8.3 or 8.4? Pick your target version. |
| 3 | Nov 9 to 15 | Make a staging copy. Update WordPress, plugins and theme there, then switch staging to the new PHP version. |
| 4 | Nov 16 to 22 | Test staging: forms, booking, checkout, payments, logins, search. Fix or replace what breaks. Apply the same plugin and theme updates on the live site. |
| 5 | Nov 23 to 29 | Service businesses: switch the live site early in the week. Stores: freeze changes through Black Friday (Nov 27). |
| 6 | Nov 30 to Dec 6 | Stores: switch after Cyber Monday (Nov 30). Everyone: watch the site closely. |
| 7 and 8 | Dec 7 to 20 | Monitor the error log, Site Health, form submissions and orders. Fix stragglers. |
| 9 | Dec 21 to 31 | Buffer. Confirm nothing on your account still runs 8.2, including old staging copies and subdomains. |
On switch day, work through this list in order:
On staging, turn on WordPress debug logging to catch warnings. Keep it off on the live site, since Site Health warns that a debug log can end up in a publicly reachable file.
Hosts handle end of life differently, and some act before PHP's own date. Three published examples:
That gives 3 likely outcomes: your host upgrades you on its own schedule, leaves you on an unpatched version, or sells extended support. Ask your host which one applies, and get the date in writing. Paid extended support can cover a site that truly can't move yet, but it's a bridge, not a plan.
This week, confirm your site has the php2shell fix, check your PHP version and ask your host about its 8.2 plans. Then book the staging test for early November, so the live switch happens with weeks to spare.
If you'd rather hand it off, we build and maintain WordPress and Laravel sites and can run the test and the switch for you. Or start with a free 2 minute video audit of your site, showing the 3 fixes we'd make first.
No. Your site keeps running on January 1, 2027. What stops is security fixes from the PHP project, so any new flaw found in 8.2 stays open. Your host may also act on its own schedule: some remove old versions from their menus, and some upgrade sites automatically. Ask your host what it plans to do and when.
Only on the patched release. PHP 8.2.35, released October 21, 2026, fixes the php2shell flaws, and 8.2 keeps getting security fixes until December 31. Confirm with your host that your site runs 8.2.35 or a patched build. Then use the remaining weeks to test and switch, rather than waiting for the last days of December.
For most WordPress sites, 8.4. The WordPress hosting handbook recommends 8.4 or later for production, WooCommerce is tested up to 8.4, and 8.4 gets security fixes until December 31, 2028. Choose 8.3 only if something you rely on isn't ready for 8.4, knowing its security support ends December 31, 2027.
No. PHP 8.6 is scheduled for November 19, 2026, which leaves little time before the 8.2 deadline, and plugins and themes need time to support a new version. php.net says not to run its release candidates in production. Move to 8.4 now, and consider 8.6 later once your plugins and theme support it.
First, update it and check for a fix from its developer. If it's abandoned, replace it with a maintained plugin that does the same job, and test the replacement on staging. As a last resort, paid extended support for old PHP versions can buy time, but it only delays the decision, so set a date to replace the plugin.
The 3 fixes we'd make first on your site, within 1 business day.