Skip to content
Website maintenance5 min readPublished: Last reviewed:

PHP2Shell: what does it mean for your website?

Check the server software as well as your CMS, and ask who is responsible for applying the relevant fixes.

Website maintenancePHPSecurity
A website maintenance checklist for PHP security updates

Current situation

If your website or a connected system uses PHP, ask the responsible host or administrator to confirm the relevant fixes and investigate signs of earlier misuse. Updating WordPress alone does not confirm that PHP on the server is patched.

PHP2Shell concerns vulnerabilities in PHP, used by WordPress and many other websites and applications. PHP issued further security releases on 19 November 2026, including fixes for the separate session issue described below. If your website uses PHP and its patch status is unknown, ask your host or administrator to check it promptly. Use the current official PHP notices and your provider's package information.

In this article

Key points

  • The PHP installation serving web requests is the relevant environment.
  • A vendor may backport a fix without changing the visible base version.
  • The October follow-up session and Windows advisories are separate checks.
  • A successful update does not rule out earlier compromise.

What PHP2Shell refers to

The name refers to CVE-2026-109618 and CVE-2026-109619. These vulnerabilities can allow unauthenticated remote code execution on affected server environments. A vulnerable installation does not automatically mean your website has been compromised.

PHP's advisory covers environments handling web requests, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. The advisory identifies particular risk with Apache mod_php, where exploitation can occur before application code runs. Ask an administrator to assess the actual deployment.

Original fixed releases and follow-up notices

The original fixes were released in PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12. These are the first listed fixed releases for those two issues, not a statement that they will always be the latest appropriate versions. Confirm an applicable patched package or suitable later release with the supplier.

On 19 November, PHP released 8.2.36, 8.3.37, 8.4.28 and 8.5.13 with fixes for the separate session issue CVE-2026-115560. The risk involves different session formats processing shared session data and can also arise between separate applications. Ask the administrator to confirm an applicable current release or vendor patch. Keep temporary measures in place until the repair and appropriate configuration have been confirmed. The 23 October notice describes the earlier situation.

On 26 October, PHP published Windows packages 8.2.35-1, 8.3.36-1, 8.4.27-1 and 8.5.12-1 for a separate Brotli issue reachable through certain cURL settings. The -1 marks a package rebuild, while the PHP runtime version stays the same. Windows hosts should therefore check the package build as well.

Check the environment that serves your website

In WordPress, the PHP version can be found under Tools, Site Health, Info, Server. If you cannot see that information, ask the administrator or host. A CMS, theme or plugin update does not replace a server-side PHP fix.

For a custom site, check the public site, CMS, APIs and connected systems. A command-line PHP version can differ from the installation serving web requests. Do not publish a detailed server-information page just to perform the check.

Codex and Claude Code are development tools, rather than server platforms. A website built with either may or may not use PHP. The production technology and connected services determine whether these particular vulnerabilities apply.

Hosted platforms and connected apps

For a standard site fully hosted by Shopify, Webflow, Wix or Squarespace, you do not manage a PHP installation for the platform itself. The provider manages that hosting environment.

Separately hosted custom apps, external integrations or self-hosted exports can still need their own check. Ask who owns each relevant component rather than assuming that one platform name describes the whole system.

Older branches and vendor patches

PHP 8.1 and older no longer receive normal upstream PHP releases. Some vendors provide extended support and backported fixes. PHP also made exceptional minimal source patches available for 7.4, 8.0 and 8.1 for this incident.

That does not restore regular support or prove that an old installation is fixed. Ask the supplier which package and patch were installed, and plan compatibility checks for moving to a supported branch.

PHP lists the end of upstream security support for 8.2 as 31 December 2026. Fixing the immediate issue and planning the next supported version are separate maintenance tasks.

Questions to send to the responsible administrator

  • Does my website or any connected application use an affected PHP environment?
  • Are the fixes for both original CVEs applied to the web-serving installation and all relevant processes?
  • Is the 19 November repair for CVE-2026-115560 applied, and does Windows package status need checking?
  • Which package or vendor patch confirms the repair?
  • Are there signs of earlier misuse, and which logs should be preserved?
  • Who will check important functions after the change?

Containment and investigation

Ask the host or server administrator to assess temporary restrictions if the environment remains exposed. A WordPress maintenance page is not proof that vulnerable PHP is protected. Temporary mitigations do not replace the security update.

If a short complete interruption is necessary, ask how the server should communicate it to search engines. Google's guidance describes a 503 response for a short outage, but duration and implementation matter and rankings cannot be guaranteed.

Amazon reported attempts against its decoy systems from 17 October, before public disclosure. That observation does not establish successful exploitation of every real website. For a potentially exposed server, ask the administrator to consider available logs from at least that period.

After patching, check important pages, login and relevant booking or shop functions through an agreed test process. Unknown administrators, unexpected files or redirects need investigation. A working website and a successful update do not prove there was no earlier compromise.

Make maintenance responsibilities explicit

Agree who monitors PHP advisories, manages the server, updates the CMS and checks backups. Those roles depend on your hosting and maintenance agreement.

Keep a supported version plan and a workable restore procedure. If you outsource website maintenance, confirm whether server updates are included instead of assuming they are part of every package.

Conclusion

If you are unsure how hosting and maintenance are divided for your website, I can help clarify the responsibilities and next step. We will agree which work is covered by existing arrangements and what needs a separate scope.

Sources

This article uses the following external sources.

Author

Timothy Hartog, SEO specialist and web designer at Hartog Growth.

Want to talk through your situation?

Contact

Let's discuss your website or visibility

Tell me what you need help with and include your website address. I will help you work out a suitable next step.