/

October 29, 2026

PHP Security Update: How to Fix PHP2Shell and Protect Your Website

Illustration of a server and business web applications with a software update arrow and shield checkmark

Technical guidance reviewed October 29, 2026.

The October 2026 PHP security update addresses two critical vulnerabilities that can allow attackers to execute code on affected servers without logging in. Known together as PHP2Shell, CVE-2026-109618 and CVE-2026-109619 affect the software behind many WordPress sites, Drupal websites, online stores, and custom business applications.

For a business owner, the immediate questions are practical: has your hosting provider applied the fixes, does your application need changes, and how do you update without disrupting sales, inquiries, or customer access?

This guide explains what to verify and how to organize the work. The priority is to patch the PHP runtime serving your website, confirm the update is active, and test the business functions that depend on it.

What Are CVE-2026-109618 and CVE-2026-109619?

These vulnerabilities are in PHP itself, rather than a particular WordPress plugin or Drupal module.

  • CVE-2026-109618: Problems in out-of-memory handling can leave internal request data in an invalid state, leading to memory corruption and potentially remote code execution.
  • CVE-2026-109619: Internal state from a request can remain accessible after the memory it refers to has been released. A subsequent request handled by the same worker can encounter that stale state, potentially enabling remote code execution.

The PHP project’s out-of-memory advisory and stale-state advisory explain the technical details.

The business implications can include unauthorized server activity and exposure of application data. A website continuing to load normally is not evidence that its PHP installation has been patched.

Which PHP Versions Include the Security Fixes?

The PHP project released these fixes on October 21, 2026:

PHP branch Upstream release containing both fixes
PHP 8.2 8.2.35
PHP 8.3 8.3.36
PHP 8.4 8.4.27
PHP 8.5 8.5.12

Use an appropriate current vendor-supported patched release, rather than treating this table as a permanent recommendation to install these exact builds. Linux distributions and managed hosts may backport fixes without displaying the corresponding upstream version number. Confirm the package revision and security status with your provider.

Older installations require particular attention. Ask the provider whether its package includes both fixes and what support remains available. An emergency patch is not a substitute for a sustainable upgrade plan.

See the PHP security announcement and subsequent updates for the official guidance.

Does Updating WordPress or Drupal Fix PHP2Shell?

Updating your CMS alone does not replace a PHP runtime security update. Your application and the server software executing it are separate parts of the stack.

For self-hosted websites, determine who maintains PHP: your managed hosting provider, server administrator, or development team. Plugin updates and security scans do not establish that the underlying runtime is patched.

Hosting arrangements matter. WordPress.com states that its hosted sites are already protected, including cases where the displayed PHP version does not match the upstream fixed releases. That assurance applies to its platform; it should not be assumed for an independently hosted WordPress installation.

How to Apply a PHP Security Update and Verify It

1. Identify Every Website and Runtime

List the production websites, subdomains, staging environments, and PHP applications your organization operates. Record the hosting provider, application owner, and update responsibility for each.

Check the PHP runtime handling web requests. A command-line PHP version can differ from the one serving your website, and different domains on one server can use different PHP versions.

For container deployments, include the image and running instances in the inventory. Updating a package on the host does not establish that PHP inside a container has changed.

2. Get a Specific Answer From Your Hosting Provider

Ask the provider to confirm:

  • Whether the runtime serving your domain includes fixes for both CVE identifiers.
  • The installed package or build revision, including any backported patches.
  • Whether all affected PHP workers or application instances have been restarted or replaced.
  • Whether the protection also covers staging sites and additional domains.

An answer such as “you are on PHP 8.2” is not sufficiently specific. Keep the provider’s confirmation with your maintenance records.

3. Prepare Backups and Focused Compatibility Tests

Confirm that you have usable file and database backups and know how to restore them. Identify custom code, extensions, plugins, and integrations that may need testing.

Distinguish patching within a PHP branch from moving a legacy application to a newer branch. The latter may involve more substantial compatibility work.

Use staging where available, but keep validation focused and prompt. If an exposed installation cannot be patched immediately, escalate to the hosting or security team for a containment decision rather than leaving it unchanged while planning a lengthy upgrade project.

4. Deploy the Update and Activate It

Use the hosting provider’s or operating-system vendor’s supported update procedure. Have the responsible administrator confirm that the updated runtime is active and all affected workers or instances have been restarted or replaced.

For containers, rebuild or obtain a patched image and redeploy the relevant instances. Installing updates without replacing the processes still serving traffic leaves an important verification gap.

5. Test the Workflows That Matter to Your Business

Checking the homepage is not enough. Validate the actions customers and staff rely on:

  • Lead generation: submit contact forms and confirm email delivery and CRM routing.
  • Ecommerce: test cart, checkout, payment handling, and order notifications using an appropriate test process.
  • Customer access: check login, password reset, and membership permissions.
  • Business applications: verify uploads, imports, APIs, webhooks, and scheduled jobs.
  • Administration: confirm staff can publish content and complete routine tasks.

Record the outcome, monitor application errors, and assign someone to resolve regressions. If an integration needs updating, our Systems Integration and API Architecture services can help address the connected workflow.

Can a Firewall or Configuration Change Replace Patching?

The PHP team states that workarounds do not provide complete protection. Firewall rules and request restrictions may reduce exposure to particular attack paths, but they are not proof that a vulnerable runtime is safe.

The October 23 follow-up also addresses an unusual session-upload-progress scenario, tracked separately as CVE-2026-115560. PHP recommends disabling session.upload_progress.enabled until the next regular bugfix release for protection against that scenario, while explaining that applications which never switch the session serialization handler at runtime can leave the feature enabled.

Have the administrator evaluate this guidance against the application and apply any required setting before request parsing, restarting affected workers. Do not present it as a standalone fix for both PHP2Shell vulnerabilities. Follow the current PHP advisory, including its configuration details.

What If a PHP Update Breaks Your Website?

A compatibility failure needs a controlled response. Returning to an unpatched public installation as a lasting workaround simply restores the original exposure.

Identify the failing component and determine whether the remedy is an extension update, plugin replacement, custom-code change, configuration correction, or broader application upgrade. Work with the host to maintain appropriate containment while that work is completed.

If legacy code repeatedly prevents security updates, treat modernization as an operational requirement. Our web platform development services support evaluating and improving custom platforms and business workflows.

Does Installing the Patch Remove an Existing Compromise?

No. Patching and investigating a suspected compromise are separate tasks.

If you find unexpected files, unfamiliar administrator accounts, suspicious redirects, or unexplained changes, preserve relevant logs and involve your hosting or incident-response team. Avoid assuming the update has removed malicious changes or invalidated stolen credentials.

Need Help Updating PHP Without Breaking Your Application?

AZ Technologies helps businesses assess PHP application compatibility, coordinate hosting changes, update custom functionality, and test the workflows that keep operations running.

A focused engagement can establish the current runtime and patch status, identify compatibility blockers, define an upgrade plan, and validate forms, checkout, customer access, and integrations after deployment.

Whether you operate a WordPress website, a Drupal platform, or a custom PHP application, start with the affected website, your hosting provider, and any known upgrade constraints.

Request a Consultation or contact AZ Technologies about your PHP update.

Frequently Asked Questions

How do I know whether my host has already patched PHP?

Ask for confirmation covering both CVE identifiers, the package revision serving your domain, and worker restarts. Managed hosts may backport fixes, so the visible version number alone may not settle the question.

Is PHP-FPM automatically protected?

No. The PHP advisory includes PHP-FPM among the web-serving installations requiring attention. Have the runtime’s patch status verified rather than relying on the server configuration’s name.

Do I need to migrate to a different hosting provider?

Not necessarily. First establish whether your existing provider supplies a supported patched runtime. Consider migration if it cannot provide a suitable maintained environment or your application has additional hosting requirements.

Can I install a WordPress security plugin instead?

A plugin does not update the PHP runtime. Confirm the server-level fix with whoever manages your hosting.

Will updating PHP improve website speed?

Performance is a separate question from confirming these fixes. If your site is also slow, use our website performance testing guide to prioritize investigation after the security work.