We may earn affiliate commissions for the recommended products. Learn more.

How shared hosting providers responded to PHP2Shell


PHP2Shell is a set of two critical vulnerabilities in PHP, an open-source server-side language used by 70% of websites on the internet. PHP2Shell could allow attackers to execute code remotely and gain control of servers running vulnerable PHP versions. PHP evaluated the vulnerabilities with a 9.2/10 score on the Common Vulnerability Scoring System v4.0 scale, marking it as high-severity.

If exploited, the vulnerability means unmitigated access to anything on a server – including websites and applications running on shared hosting environments. Shared hosting users have almost no way to deal with security issues like PHP2Shell. They rely on hosting providers to fix the issue.

The Cybernews research team investigated how and when shared hosting providers responded to the PHP2Shell incident. This includes proactive mitigations, communication transparency, reliance on third-party vendor schedules, and backporting support for legacy PHP versions.

For shared hosting customers, the incident shows that an official patch release does not guarantee immediate protection across all shared hosting environments. Evaluating a provider's historical response – pre-patch mitigations, support for outdated software stacks, and clear security status verification guidance – remains crucial when choosing a secure hosting environment.

Key takeaways:

Why was PHP2Shell critical for shared hosting?

Shared hosting environments are among the most affected by the PHP2Shell vulnerabilities. If an attacker exploits a vulnerable PHP application to gain shell access, the extent of potential and actual damage largely depends on the security measures that a hosting provider deploys. Unlike dedicated hosting, where users can manage operating system settings, security policies, and access controls, shared hosting customers depend on their hosts.

Clear and timely communication remains essential even if a hosting provider does not use the specific vulnerable technology. Many shared hosting users may lack the technical expertise to fully understand the risks and their potential impact. Providing accurate and understandable information, action points for individual users, and acting quickly as incidents occur all lead to better, more secure outcomes for both the hosts and their customers.

Investigation approach

This report investigates how shared hosting providers differed in their response to PHP2Shell beyond deploying security updates:

  • How did providers communicate their actions, progress, remaining risks, and customer responsibilities?
  • How did providers protect customers using unsupported PHP versions? What operational consequences did mitigation and patching have for customers?
  • What role did CloudLinux, cPanel, and other infrastructure or security vendors play?
  • How did remediation timelines and rollout methods differ?
  • What measures did providers introduce before official PHP patches were available?

The Cybernews content researcher Jovita Kirlytė monitored and reviewed official statements, status updates, and press releases from 11 shared hosting providers: Hostinger, Bluehost, IONOS, GoDaddy, DreamHost, SiteGround, ScalaHosting, HostGator, Hosting.com, Namecheap, and WordPress.com (Automattic). The overall response highlights key operational differences among shared hosting providers, beyond the deployment of upstream patches. While every evaluated host addressed the vulnerability, their strategies varied.

Kirlytė also observed user responses about given hosting providers and PHP2Shell on Reddit to understand what actual users consider important when it comes to patching vulnerabilities and responding to security incidents. However, the sample size is too small to make any general conclusions – Reddit is simply a glimpse into how shared hosting users were reacting to the incident.

The investigation findings concern the hosts’ reported response. This means that there is not enough independent evidence to conclude that a given provider handled the PHP2Shell vulnerabilities better or worse than other hosts. The available sources document announced actions rather than independently measured and verified results.

Timeline

The vulnerabilities were discovered using AI and initially disclosed to PHP by security researchers back in August 2026. Yet, PHP announced PHP2Shell’s existence ahead of schedule on October 20th as details of the flaws emerged elsewhere on the internet. This forced providers to respond before official patches are available.

ScalaHosting did not provide status reports or updates. WordPress.com/Automattic received updates directly from PHP and deployed patches before the initial vulnerability announcement and fixed builds were released. Further, as of November 16, 2026, Namecheap has removed its October 21 update from the status page, and it is currently only available in its archived form. Full update information is available from a status aggregator.

All times are in UTC. However, different providers are based in different time zones, which may have affected their response speed.

October 21

  • 07:00: SiteGround reports deploying server-level security rules. It also disables affected functionality across supported PHP versions before installing the official patches later that day.
  • 07:01: Hosting.com announces maintenance for security checks.
  • 13:46: DreamHost announces it has implemented protections across all of its hosting platforms.
  • 14:00: PHP releases official fixes. Providers can begin applying fixed builds depending on their own packaging systems, infrastructure, and third-party vendor availability.
  • 14:40: NameCheap starts installing fixed builds across its servers.
  • 15:34: IONOS announces it’s going to update its systems.
  • 16:04: DreamHost begins rolling out fixed builds across all servers
  • 17:18: Bluehost and HostGator begin deploying patches across their servers.
  • 17:44: Hostinger announces its environments are not affected, but that it has implemented extra protection layers against known attacks. The host also starts rolling out patched PHP versions across its infrastructure.
  • 17:50: Namecheap announces final patch deployment is in progress.
  • 19:12: Hostinger completes patch deployment for its Agency Hosting infrastructure.
  • 19:30: GoDaddy completes patching all PHP versions across its Managed Hosting for WordPress services. It deploys several mitigations to its Web Hosting and Windows Hosting services while waiting for a vendor to supply custom PHP packages.
  • 22:00: Hosting.com begins deploying patches it received from its third-party vendors.
  • --:--: Siteground completes deploying fixed builds across its servers.

October 22

  • 01:20: GoDaddy completes patching Windows Hosting servers, and continues deploying custom patches to its Web Hosting servers.
  • 03:34: Hostinger completes cPanel fixed build deployment.
  • 04:00: Bluehost and HostGator have successfully patched most of their servers.
  • 05:59: DreamHost completes security updates across most of its services and executes final tests before completing deployment.
  • 06:44: Hostinger completes PHP patch deployment across its servers.
  • 07:12: IONOS announces its Website Builder and Control Panel systems are functioning normally.
  • 07:59: IONOS announces all services are functioning normally.
  • 10:32: IONOS completes official update rollouts across all servers it operates.
  • 13:30: GoDaddy completes patching its Web Hosting servers.
  • 15:00: Bluehost and HostGator announce their teams are progressing with patched PHP build deployment across the infrastructure.
  • 16:50: Namecheap completes patched build deployment across all of its servers.
  • 18:26: DreamHost completes security updates across all of its servers.
  • 23:00: Bluehost and HostGator have deployed patched PHP builds across most of their infrastructure.
  • 23:02: Hosting.com completes deploying fixed PHP builds and concludes the maintenance of its servers.

October 23

Third vulnerability is disclosed, requiring providers to reassess their current mitigations. This is a separate vulnerability and not a third PHP2Shell flaw – it wasn’t taken into account when assessing provider responses in this investigation.

How shared hosting responded to PHP2Shell: main findings

Looking at the timeline of the October 2026 PHP2Shell vulnerability events and quality of incident reports from shared hosting providers, we can see different response patterns emerge. Clarity and extent of communication regarding the vulnerabilities is by far the biggest and most important difference.

Providers also responded differently to details about the vulnerabilities prior to the official announcement – some deployed mitigation measures right away, and others were delayed by reliance on third-party vendors providing custom patches. Some providers also skipped patching (backporting) older PHP versions, forcing users to quickly upgrade to newer, patched versions.

Different communication strategies

Looking at shared hosting provider status updates and related Reddit discussions makes clear that confirming patch deployment completion doesn’t always give users enough information to assess whether their hosting environment is protected. Documenting remediation efforts through updates is not always enough. It doesn’t guarantee that users will receive, notice, or understand them.

Individual hosting provider responses differ in their amount of detail, frequency, and action points for users. IONOS, Namecheap, GoDaddy, and Hostinger provided some of the more detailed status updates. The updates included information like which services (e.g. managed, reseller, WordPress hosting, etc), and individual servers in Namecheap’s case, have received the patches, and which are in progress.

Bluehost and HostGator, owned by the Newfold Digital conglomerate, published detailed lists of patched PHP packages across hosting configurations and operating systems. By contrast, ScalaHosting and WordPress.com did not publish status updates at all. ScalaHosting focused on answering individual customer support questions and identified older PHP versions that require migration.

Customer reactions to host communication

The reception of shared hosting communication regarding PHP2Shell is somewhat reflected in hosting provider-specific Reddit threads. Although the sample is small, these discussions show a gap between communicating security fix deployment and actually helping users understand whether they received protection.

Version-based security scans can report a supposedly outdated installation, even when a relevant vulnerability has been fixed. However, backported fixes left the PHP version numbers unchanged, so it was hard for users to distinguish patched installations from vulnerable ones.

While Hostinger, Godaddy, and Namecheap provided guidance on how to check the patch status of specific PHP versions, some users discussing those providers were confused whether their servers are protected. Customer support across most providers was deemed largely unsupportive, providing incorrect, conflicting, or generic information.

When it came to official communication and status reports, users were frustrated with a lack of clear communication about what mattered most. They described Hostinger’s lack of initial proactive communication as “radio silence.” They also expressed frustrations with HostGator keeping silent about the vulnerability, yet still sending promotional material.

Some Bluehost users had to take their sites offline, since the host’s security updates caused unexpected server downtime. The updates and potential downtime were not communicated in advance via status update pages or alerts.

Delayed by third-party vendor dependencies

The official PHP patches were released on October 21, but not all providers could deploy them immediately. However, many shared hosting platforms use customized PHP builds maintained by third-party vendors such as CloudLinux in the case of Namecheap. These packages must be updated and distributed before hosting providers can install the fixes across their infrastructure, which will inevitably affect deployment speed.

This is especially visible in GoDaddy and Namecheap’s responses to the incident. While GoDaddy’s Managed Hosting for WordPress had already been patched by 19:30 UTC on October 21, due to the wait for custom packages from a third-party vendor, Web and Windows Hosting patches were deployed only the next day by 13:30 UTC.

Similarly, NameCheap’s partnership with CloudLinux caused delays in deploying fixes – the patched packages reached CloudLinux staging repositories only at 20:40 UTC on October 21, and deployment completed at 16:50 UTC the next day. Namecheap also reported issues with the PHP version numbers not changing despite having received backported security fixes.

ScalaHosting faced a different problem: overloaded external software repositories. High demand for PHP patches caused download timeouts, and the new packages in the repository mirrors had not yet synchronized. The host reported patching most servers within eight hours of the official release, with the remaining systems updated by the following morning.

Late patch deployment is a security concern

The shared hosting dependence on third-party vendors and delays in deploying patches highlights an important security concern. When a publicly available security patch is not always immediately usable, servers remain exposed to exploitation for longer. As Huntress notes, this extended window of vulnerability is highly dangerous. Because shared hosting security tends to be monitored less closely, any attacks that occur before a patch is deployed are much harder to detect.

For example, users on Reddit reported that due to patching delays, some DreamHost customer sites were being actively exploited. Slow patching from GoDaddy, DreamHost, and Namecheap also caused widespread concern.

By contrast, the rest of the web dealt with the PHP vulnerabilities rather quickly. WordPress received patches from PHP before the vulnerabilities and fixes were shipped. Individual web development agencies were also quick to patch their environments, with some managing to do so within 30 minutes of patch release. Meanwhile, Cloudflare reported that it had deployed WAF protections for all its customers “about 9 hours ahead of public disclosure,” at 03:02 UTC.

Handling outdated PHP versions

PHP 8.1 and older versions were outside the official security maintenance lifecycle when the PHP2Shell fixes were released. Shared hosting providers had to get backported fixes for older versions or require customers to upgrade.

A backported patch applies a security fix to an older software version without requiring a full upgrade to a newer PHP release. For websites running older applications, a PHP upgrade can require code changes, dependency updates, and compatibility testing. Users whose hosts automatically deployed backported fixes could avoid those immediate tasks.

However, backporting has limitations. Fixing PHP2Shell on an unsupported PHP version does not make that version fully secure. Other vulnerabilities may remain, and continued protection depends on whether the provider or its software vendor maintains that branch.

Hosting providers handle outdated PHP versions differently because they rely on different sources for security patches. Providers like Namecheap, Hosting.com, and GoDaddy use third-party software vendors, such as CloudLinux, which supply backported patches for old PHP versions. IONOS uses a specific extended support service to maintain legacy coverage. By contrast, ScalaHosting did not have backported patches available for PHP 7.3 and older. When a provider cannot get a vendor patch for an unsupported version, it must force customers to upgrade to a newer PHP release.

Conclusion

Ordinary users usually do not have access to servers or enough expertise and instead rely on their hosting providers to patch up the servers. If a vulnerability is found, the responsibility to deal with it falls on the host. Provider transparency, rapid response in deploying patches, and clear communication are key in such situations. How much current and future users trust a hosting provider will depend heavily on its response to security incidents.

With AI entering the cybersecurity domain, chances are security incidents and vulnerability findings will only increase in the upcoming years. If you are someone using shared hosting to host your website or projects, it’s important to understand your provider’s communication and incident response strategy. When your subscription expires, it can help you decide whether to stay or to migrate your projects somewhere else. In a world where trust is hard to find and hard to maintain, investigate closely and choose wisely.