Security guide · PHP2Shell
How to update your WordPress site for PHP2Shell
Two critical flaws in PHP, the language WordPress runs on, can let an attacker take over a website's server without logging in. Attacks are already being reported. Here's how to check your site and update it safely, step by step.
Patched PHP versions (or newer)
PHP 8.1 or older? No fix is coming for those versions. Your site needs to move to a newer one.
CVE-2026-109618
CVE-2026-109619
Time: 30 to 60 minutes for most sites. You'll need your WordPress admin login and your hosting account login.
-
1
Check which PHP version your site runs
- Log in to your WordPress dashboard (usually yoursite.com/wp-admin).
- Go to Tools, then Site Health.
- Click the Info tab and open the Server section.
- Find PHP version and compare it with the patched versions above.
Already on a patched version? You're covered for PHP2Shell. Steps 2 and 3 are still worth doing; they're the routine that keeps the next problem from becoming yours. -
2
Back up your site first
If an update breaks something, a backup is how you get back to a working site in minutes instead of days.
- Log in to your hosting account and look for Backups. Most hosts have a one-click backup or restore point.
- No backup tool at your host? Use a WordPress backup plugin.
- Make sure the backup includes both your files and your database.
- Before moving on, find the Restore button, so you know where it is if you need it.
-
3
Update your plugins, theme and WordPress
Newer PHP versions can break old plugins. Updating them first makes the PHP switch in step 4 far less likely to cause trouble.
- In WordPress, go to Dashboard, then Updates.
- Update your plugins first, then your themes, then WordPress itself.
- Go to Plugins and delete any you don't use. Do the same under Appearance, Themes, keeping your active theme.
- For each remaining plugin, check Last updated on its page in the WordPress plugin directory. A plugin nobody has updated in years is the one most likely to break, so look for a maintained replacement.
-
4
Update PHP at your web host
PHP lives on your hosting account, not inside WordPress, so this step happens in your host's dashboard.
Hosting with cPanel
- Open Select PHP Version or MultiPHP Manager.
- Choose the domain for your website.
- Pick a supported version and click Apply.
Managed WordPress hosting
- Open your site in the hosting dashboard.
- Look for a PHP version setting, often under tools, settings or advanced.
- Can't find it? Ask your host's support to do it for you.
Which version? PHP 8.3 is the safe choice for most WordPress sites today. Choose 8.4 if your theme and plugins support it.
The step most people miss: picking "8.3" chooses the version family, not the patch. Your host decides whether you're on the patched 8.3.36 or an older 8.3 build. Ask their support, and keep their answer in writing:
“Is my site running a PHP build patched for CVE-2026-109618 and CVE-2026-109619?”
Some hosts patch their own builds without changing the version number, so their confirmation matters more than the number you see.
-
5
Test your site
- Clear your caching plugin and your host's cache, if you have them.
- Open your homepage and your most important pages in a private browser window.
- Send a test through every form and make sure the email arrives.
- If you take bookings or payments, run a test of those too.
- Log out and back in to WordPress, then check Tools, Site Health, Info, Server to confirm the new PHP version.
-
6
If something breaks
Don't panic. The cause is almost always one outdated plugin.
- Check your email. WordPress often sends the site's admin email a “technical issue” message with a link that lets you log in safely and see which plugin failed.
- Deactivate that plugin, or deactivate plugins one at a time until the site works, then replace the culprit.
- Still stuck? Restore the backup from step 2, and get help before trying again.
Avoid staying on an old, unpatched PHP version to keep a plugin running. That leaves the door open this whole guide is about closing.
Can't update today?
Ask your host for a temporary safeguard
Security researchers suggest a stopgap while you get to the update: ask your host to set session.upload_progress.enabled = 0
(and, on PHP 8.5, fatal_error_backtraces = 0), then restart PHP. It reduces the risk. It doesn't replace the patch.
On Wix, Squarespace or Shopify?
Those platforms run the servers for you, so there's no PHP setting for you to change. Updates like this are their job.
Another PHP site (Joomla, Drupal or custom)?
Steps 2, 4 and 5 apply the same way: back up, move to a patched PHP release, and test.
Rather have it done for you?
Have Rengie update your site.
Every step on this page, handled for you, with someone who's done it before watching for what breaks.
- A full backup before anything changes
- Plugins, theme and WordPress updated
- PHP moved to a release patched for PHP2Shell, confirmed with your host
- Your pages, forms and logins tested afterward
- A short written summary of what was updated
Website Security Remediation
$297one-time, per site
For one WordPress website. After checkout, we'll set up secure access to your WordPress and hosting accounts. Never email us a password.
Have Rengie update my siteQuestions first? Book a 15-minute call
Sources: the PHP project's October 21, 2026 security releases, and advisories from Rapid7, Tenable, Palo Alto Networks Unit 42, Huntress, Google Cloud, Datadog Security Labs and Red Hat. Researchers disagree on how easy these flaws are to exploit; all agree the fix is to move to a patched PHP release.