Skip to content

Is my website affected by PHP2Shell, and what do I do now?

The short answer

Treat an unpatched PHP site as affected by PHP2Shell. Two critical PHP flaws can let attackers run code without logging in. Ask your host to confirm PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35, a later release of those branches, or a patched host build is installed and running. For PHP 8.1 or older, plan an upgrade to a supported branch. Check your PHP version in your hosting panel; updating your CMS alone does not update PHP.

Key takeaways

  • The flaws are in PHP, not in your CMS, so updating WordPress, plugins or themes alone does not fix them.
  • The fixed releases are PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, and any later release of those branches. Some hosts patch older builds without changing the number.
  • PHP 8.1 and older are end of life, and PHP 8.2 joins them on 31 December 2026.
  • A web firewall can block known attacks while you patch. Only updating PHP fixes the flaw.
On this page
  1. What happened
  2. Is my site affected?
  3. How to find your PHP version
  4. Which versions are fixed
  5. What end of life means for PHP 8.1 and older
  6. What your host and your firewall cover
  7. Questions to ask your developer or host
  8. How we can help
  9. Questions people ask
  10. Sources
  11. Read next

Most website security news is about one plugin or one theme. This one is different. PHP is the language that runs the code of WordPress, Drupal, Joomla and Laravel sites on the server, and on 21 October 2026 the PHP project fixed two critical flaws in PHP itself, now known as PHP2Shell. Because they sit underneath your CMS, a site on an unpatched PHP can be exposed however carefully its own code was written.

What happened

  • Two flaws, one name. CVE-2026-109618 and CVE-2026-109619 are both rated 9.2 out of 10, critical. PHP says they "can allow unauthenticated remote code execution": someone who has never logged in can make your server run their code.
  • Every web setup is at risk. PHP names "all PHP installations serving web requests", including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. It rates Apache with mod_php highest, because there the attack can work before any of your site's code runs.
  • Old versions too. Wiz, one of the research teams that reported the flaws, says versions going back to PHP 5.4 are affected. It showed the attack working against the latest WordPress, Drupal and Joomla container images.
  • Attackers are using it. On 26 October the US Cybersecurity and Infrastructure Security Agency (CISA) added both flaws to its catalog of vulnerabilities known to be exploited. Canada's Cyber Centre says open-source reporting shows both being exploited in the wild.

Is my site affected?

Work through three questions.

  1. Does it run on PHP? WordPress, Drupal, Joomla, Magento and Laravel sites do, and so do many custom-built sites. If you are not sure, ask whoever built it.
  2. Which PHP version does it run? The next section shows how to find out.
  3. Is that version fixed? Compare it with the table below. If it is older than the fixed release for its branch, treat the site as exposed until your host confirms otherwise.

Updating WordPress, your plugins or your theme will not fix this on its own. Cloudflare's write-up says it plainly: updating website code or plugins alone "does not fix these vulnerabilities". The PHP software on the server has to be updated.

How to find your PHP version

  • In your hosting panel. cPanel's MultiPHP Manager lists the PHP version each of your domains uses. In Plesk, the versions show in each handler's name under Tools & Settings, then PHP Settings. Other panels have a similar page.
  • In WordPress. As WordPress's own guide explains, go to Tools, then Site Health, open the Info tab, expand Server and look for PHP version.
  • With a phpinfo check. Upload a file with a name that is hard to guess, containing only <?php phpinfo();, open it in your browser and note the PHP version at the top. Then delete the file straight away: phpinfo also prints your server's settings, paths and environment, which you do not want public.
  • Ask your host. The questions at the end of this guide are written so you can paste them into a support ticket.

One catch: some hosts and Linux distributions fix an older version without changing its number. Ubuntu 24.04's fixed package is still numbered 8.3.6 (8.3.6-0ubuntu0.24.04.13 in full), and Plesk's fixed PHP 8.1 build is still 8.1.34, told apart from the old one by a build date of 21 October 2026 or later. If your number looks old, ask your host whether your build includes the fix before you assume the worst.

Which versions are fixed

Your PHP versionFixed in (or later)Security fixes from PHP until
8.58.5.1231 December 2029
8.48.4.2731 December 2028
8.38.3.3631 December 2027
8.28.2.3531 December 2026
8.1 and olderNo release from PHP; some hosts and vendors ship patched buildsAlready ended

PHP gave Linux distributions and long-term support vendors the patches before the release, so check with yours for updated packages; theirs may carry their own version numbers.

What end of life means for PHP 8.1 and older

PHP supports each version for four years: two years of full support, then two years of fixes for critical security issues only. After that the version reaches its end of life and is no longer supported. PHP 8.1 reached that point on 31 December 2025, PHP 8.0 on 26 November 2023 and PHP 7.4 on 28 November 2022.

For PHP2Shell, that means:

  • No release from PHP. PHP 8.1 and older no longer receive updates from the PHP project. Given how serious these flaws are, PHP published minimal source patches for 7.4, 8.0 and 8.1, for people who build PHP themselves.
  • Your host may have patched it anyway. cPanel shipped fixes for its PHP 7.4 to 8.5 packages on 21 October, Plesk shipped fixed builds of 7.4, 8.0 and 8.1 for Linux, and Ubuntu has fixes for its older releases through its Ubuntu Pro service. A patched build closes this hole. It does not bring the version back into support.
  • CISA's advice is blunt. Organisations that cannot update now, or that still run PHP 8.1 or earlier, should take those systems offline until they are patched or updated.
  • PHP 8.2 is next. Its security fixes end on 31 December 2026. If you are moving anyway, move to 8.3 or later; WordPress already recommends 8.3 or higher.

Moving to a newer PHP is usually the real fix, and it needs care. WordPress says it cannot know whether your themes or plugins will work on a newer version, and that they should be tested. Take a backup first and test the site on the new version before you switch.

What your host and your firewall cover

Your host. If your host manages PHP for you, applying the update is their job, and Cloudflare's advice is to ask them to apply it. Confirm two things:

  • That your site is actually on a fixed build. In cPanel, each domain can use a different installed PHP version, so one site on an account can be patched while another is not.
  • That PHP was restarted after the update. Google's guidance is that updating the packages on disk leaves the vulnerable code running in PHP processes that were already started, until they are restarted.

Updating PHP is also separate from updating your site's plugins, theme and code, and from moving it to a newer PHP version.

Your firewall. A web application firewall filters traffic before it reaches your server. Cloudflare switched on rules against PHP2Shell for every plan with its firewall, including the free plan, from 21 October, and Google Cloud published rules for its Cloud Armor firewall. CISA says a web application firewall "may provide some protection until systems are updated or patched". Treat it as a way to buy time:

  • Rules match known attacks, and attackers change them. Cloudflare says it watched attackers "mutating the attack payload to try to bypass our protections".
  • On 23 October PHP disclosed a related, unlikely attack path that the 21 October releases do not fix. Cloudflare's rule for it does not cover sites that have changed a PHP setting called session.upload_progress.name.
  • PHP says only an update is a complete solution.

Questions to ask your developer or host

Copy these into an email or a support ticket.

  1. Which PHP version does our site run, and does that build include the fixes for CVE-2026-109618 and CVE-2026-109619?
  2. When was it updated, and were PHP-FPM or Apache restarted afterwards?
  3. Are we on PHP 8.2 or older? If so, what is the plan, and the date, for moving to 8.3 or later?
  4. Is session upload progress switched off (session.upload_progress.enabled=0) until PHP's next release, as PHP suggests?
  5. Is everything else we run on PHP patched too, such as a staging copy, admin tools, webmail or Docker images? CISA notes that PHP is often part of other software.
  6. Is the site behind a web application firewall with the PHP2Shell rules switched on, and can the server be reached any other way?
  7. Do we have a recent backup, and when was a backup last restored?
  8. Do our plugins, theme and code work on the PHP version we are moving to, and who tests that?

If the answers come back unclear, or your site needs work before it can move to a supported PHP, our PHP fix and upgrade covers one website or app for a flat fee.

How we can help

  • PHP moved to a supported, patched release, with your CMS or framework core, plugins, themes and Composer packages updated, small breakages fixed, a backup first and a before-and-after report. Larger upgrades are quoted separately. PHP fix and upgrade.
  • Hardening, security headers, encryption and attack monitoring for your site, apps and servers. Cybersecurity.
  • After launch: dependency and security updates applied before they pile up, from a named engineer who knows your system. Maintenance retainers.

Questions people ask

Does updating WordPress or my plugins fix PHP2Shell?

No. The flaws are in PHP itself. Cloudflare's advice is that updating website code or plugins alone does not fix them: the PHP software running the site has to be updated, and if your host manages PHP, ask them to apply the update.

Is a web firewall enough?

No. Firewall rules from Cloudflare, Google Cloud and others block known attack patterns, and CISA says a web application firewall may provide some protection until systems are updated. PHP says only an update is a complete solution.

My version number is older than the fixed one. Am I exposed?

Not necessarily. Some distributions and hosts patch without changing the PHP version: Ubuntu 24.04's fixed package is 8.3.6-0ubuntu0.24.04.13, and Plesk's fixed PHP 8.1 build is still 8.1.34, built on 21 October 2026 or later. Ask your host whether your build includes the fixes for CVE-2026-109618 and CVE-2026-109619.

We are on PHP 7.4. What now?

PHP 7.4 reached end of life on 28 November 2022, and PHP 8.1 and older no longer receive updates from the PHP project. For PHP2Shell, given the severity of the flaws, PHP published minimal source patches for 7.4, 8.0 and 8.1, and some hosts ship patched builds. Plan a move to a supported version. CISA's advice for systems still on PHP 8.1 or earlier is to take them offline until they are patched or updated.

Sources

  1. PHP: Security advisory, critical remote code execution vulnerabilities (21 October 2026)Checked 4 November 2026
  2. PHP: Informational advisory, session upload progress (23 October 2026)Checked 4 November 2026
  3. PHP: Supported versionsChecked 4 November 2026
  4. PHP: Unsupported branchesChecked 4 November 2026
  5. GitHub advisory GHSA-w8hw-w9fx-j79w (CVE-2026-109618)Checked 4 November 2026
  6. GitHub advisory GHSA-6wmf-4rv5-p3rp (CVE-2026-109619)Checked 4 November 2026
  7. CISA: Critical vulnerabilities in PHP require immediate patchingChecked 4 November 2026
  8. CISA: Known Exploited Vulnerabilities catalogChecked 4 November 2026
  9. Canadian Centre for Cyber Security: AL26-026, critical vulnerabilities impacting PHPChecked 4 November 2026
  10. Wiz Research: PHP2ShellChecked 4 November 2026
  11. Cloudflare: Cloudflare deploys protections against php2shell vulnerabilityChecked 4 November 2026
  12. Google Cloud: Responding to core PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619Checked 4 November 2026
  13. Ubuntu: USN-8948-1, PHP vulnerabilitiesChecked 4 November 2026
  14. Ubuntu: CVE-2026-109618 (fixes for older releases through Ubuntu Pro)Checked 4 November 2026
  15. cPanel: Release notes (EasyApache 4 25.91 and the cPanel & WHM security update)Checked 4 November 2026
  16. cPanel: MultiPHP Manager for cPanelChecked 4 November 2026
  17. Plesk: Security updates for PHP CVE-2026-109618 and CVE-2026-109619Checked 4 November 2026
  18. WordPress: Update PHPChecked 4 November 2026
  19. Laravel: InstallationChecked 4 November 2026
  20. PHP manual: phpinfoChecked 4 November 2026

Other companies change their prices and fees. Check the source before you rely on a figure.

Not sure what your site runs on?

Send us your website address and where it is hosted. We reply within one working day.