Account Manager 
Login ID    Password  
 
 Forgot your password?
home  » Customer Support
 
Customer Support
 
Top

October 2026 PHP Vulnerability FAQ

Overview

We're updating PHP across our hosting servers in response to recently discovered critical security vulnerabilities.

PHP is the software behind many websites, including WordPress, shopping carts, and custom applications. Most websites should continue working normally after the update, but some older scripts may need adjustments.

We're also making newer PHP versions available so customers can gradually move away from outdated software.

About the security update

On October 21, 2026, the PHP development team released fixes for two critical security vulnerabilities that could allow attackers to execute code on affected web servers.

We're updating our hosting environment to address these risks.

We are not suggesting that your website has been compromised.

This is a preventive security update. A vulnerability being discovered does not mean anyone has exploited it on your website.

We're primarily changing the PHP software that runs your website, not your website's content or files.

Most sites should continue working normally. However, older applications may rely on PHP features that have changed or are no longer supported.

We recommend checking:

  • Your homepage and important pages.
  • Contact forms and other interactive features.
  • Login and administration pages.
  • Shopping carts, checkout pages, and payment processing, if applicable.

If something isn't working, please contact us with the affected URL and a brief description.

Contact our support team by replying to the notification email.

We can help identify whether the problem is related to PHP compatibility and discuss the available options.

The update primarily affects website scripts that run PHP. Ordinary email delivery and DNS services are not part of the PHP upgrade.

Web-based applications, including some webmail interfaces, may be affected if they depend on older PHP code.

PHP versions and compatibility

Our two preferred options are:

  • PHP 8.5.12 -- Recommended for websites compatible with modern PHP. It provides the longest official support window of these two choices.
  • PHP 8.2.35 -- An alternative for websites that need additional time to become compatible with newer PHP releases.

Both contain the official October 2026 security fixes.

We're working to make these versions available throughout our hosting environment. Availability may vary by server during the rollout.

Important: PHP 8.2 reaches its official end of life on December 31, 2026. It should be considered a transitional option, not a long-term solution.

Some older websites cannot run on newer PHP versions without changes.

To help with compatibility, we've developed custom PHP builds with selected security fixes applied to older releases. This process is called backporting.

These builds help us avoid suddenly breaking older websites, but they are temporary solutions and do not provide the same ongoing security coverage as officially supported PHP releases.

Backporting means taking a security fix developed for a newer software release and adapting it to an older version.

This allows older applications to keep working while addressing specific security problems.

However, a backported fix does not mean an old PHP version is fully secure or officially supported. Other vulnerabilities may remain.

Some older websites rely on features removed or changed in newer PHP versions.

Forcing every website onto the latest version could cause unnecessary breakage. We're trying to balance security with compatibility while giving customers time to modernize.

Yes. Our older compatibility builds are intended as temporary solutions.

We expect to phase out outdated PHP versions and eventually require customers to use newer, officially supported releases.

We haven't announced a final migration deadline yet. We'll try to provide reasonable advance notice, although urgent security issues may sometimes require faster action.

Possibly.

Updating PHP does not automatically update WordPress, plugins, themes, or other applications.

Older software may need updates to work with modern PHP. Keeping your website software updated is also important for security, regardless of the PHP version.

Technical questions

On supported ActionWeb servers, PHP versions can be selected through Apache configuration, including .htaccess overrides.

This can allow an entire website, or an individual directory, to use a different registered PHP version.

The available choices depend on the hosting server. Contact us if you need help identifying a compatible option.

Some ActionWeb websites use directives such as AddType to select PHP.

For example, an older configuration might contain:

AddType application/x-httpd-php54 .php

This example selects an old PHP handler and is not a recommended configuration.

To switch to a patched version:

  1. Back up your existing .htaccess file.
  2. Identify any existing PHP version overrides.
  3. Replace the old handler with the supported handler name for your hosting server.
  4. Test your website, including any directories with separate .htaccess files.

Important: The exact handler names vary by server and must be registered before they can be used. Contact us for the correct settings rather than guessing.

Yes, where the hosting server supports directory-level overrides.

For example, an older application in one directory might need a different PHP version than the rest of the website.

This can be helpful during migration, but the application and its dependencies must be compatible with the chosen version.

You can ask our support team to verify the version actually processing your website's requests.

For developers, PHP's PHP_VERSION constant can report the running version from within a web script. Note that the command-line PHP version may differ from the version used by your website.

We may be able to move your website to another compatible patched PHP version.

However, restoring a version with known unpatched security problems may not be an available option.

  • Keep WordPress, plugins, themes, and other software updated.
  • Remove applications and plugins you no longer use.
  • Use strong passwords and multifactor authentication where available.
  • Maintain backups before making major changes.
  • Plan to migrate to a currently supported PHP version.

A patched PHP runtime helps protect the server, but it does not fix vulnerabilities in website applications themselves.

The official PHP website provides details about the October 21, 2026 security releases:

https://www.php.net/archive/2026.php

You can also check the official PHP support schedule:

https://www.php.net/supported-versions.php

Contact our support team. We can help identify the PHP compatibility issue and discuss possible solutions.

Our immediate priority is addressing the security vulnerability. We'll continue working with customers on longer-term compatibility and migration needs.

Last updated November 2, 2026
[ Services | Reseller  | Privacy Policy | Terms of Service | Contact | Support  ]
Copyright © 1996 - 2020 iSparks, Inc, All Rights Reserved.