Managed web hosting
The provider typically installs PHP security fixes. You confirm its latest advisory, your plan's coverage, and any custom runtimes.
PHP2SHELL / HOSTING PROVIDER TRACKER
Find out what 20 major hosting and cloud providers say about their PHP security response, who's responsible for fixing each service, and what you should do next.
Reviewed October 23, 2026 · 20 providers · 46 service types · Source-linked, manually curated snapshot
THE IMPORTANT DISTINCTION
Shared hosting usually leaves PHP patching to the provider. A self-managed VPS usually leaves it to you. Cloud and application platforms can split responsibility between base-image updates and customer redeployment.
The provider typically installs PHP security fixes. You confirm its latest advisory, your plan's coverage, and any custom runtimes.
You generally patch the operating system or PHP runtime yourself, restart workers, and test the actual web-serving application.
The vendor may patch a base image while your team must rebuild, redeploy, or explicitly enable a platform update.
THE PROVIDER-BY-PROVIDER RESPONSE
Select your service type, search your provider, or filter by responsibility and patch status. Expand a provider for official guidance, recommended action, and where Edgar Tech can help.
Provider advisory: Read official statement ↗ Additional vendor guidance ↗
Important: Use the AWS bulletin and Amazon Linux security notices; WAF rules offer only temporary defense in depth.
AWS has published patched PHP platform versions. With Managed Platform Updates enabled, an update is applied during the configured maintenance window; verify the environment platform release after that window.
Patch status audit and safe upgrade scheduling.
If managed updates are not enabled, deploy the updated Elastic Beanstalk platform yourself and verify the live environment.
Version upgrade, rollback and validation.
AWS does not manage PHP installed inside your VM. Apply the appropriate OS vendor package fixes and restart services; Amazon Linux patches are available for supported repos.
Automated patching and evidence collection.
AWS does not provide a managed PHP Lambda runtime; rebuild your custom runtime/container with patched PHP and redeploy.
Image/runtime modernization and deployment tests.
Provider advisory: Read official statement ↗
Important: Status is not an assertion that any individual Bluehost site is still vulnerable. Vendor lists patched package versions.
Bluehost reports staged deployment and interim mitigations. Ask support for the exact server/product's patch completion and validate vendor build evidence.
Verification or coordination if a specific environment remains outstanding.
Bluehost directs VPS/dedicated administrators to monitor notices and apply the current cPanel, Plesk, CloudLinux or OS security packages themselves.
Vendor-specific patch and validation.
Provider advisory: Read official statement ↗
Important: Cloudways reports separate mitigations for CVE-2026-115560 (October 23); do not conflate that issue with the October 21 fixes.
Cloudways says all active servers were updated by October 22 and the PHP2Shell incident closed October 23; contact support if they notified you of an exception.
Independent runtime verification; custom application smoke tests.
Provider advisory: Read official statement ↗
Important: DigitalOcean distinguishes its own infrastructure from PHP installed inside customer compute; Cloudways is a separately managed product (listed above).
DigitalOcean says patched runtimes/buildpacks are available; redeploy the application/function to activate them. Custom Dockerfiles must use patched base images.
Safe build/redeploy, runtime verification and tests.
Previously deployed Droplets and Marketplace app images do not automatically receive PHP updates. Update packages/images and restart affected processes.
Fleet inventory, package patching, testing.
Rebuild container images using a trusted patched runtime and redeploy workloads.
CI/CD image update and rollout.
Provider advisory: Read official statement ↗
Important: Provider's status statements remain the source of truth for the individual service.
DreamHost reports applying the official PHP updates across its hosting platforms. Confirm any older Extended Support runtime's specific backport.
Verification and supported-version planning.
DreamHost reports network-wide security work, but independently installed/custom PHP may not be covered. Confirm your product's responsibilities with DreamHost and inspect the serving runtime.
Responsibility assessment and patching if customer-managed.
Provider advisory: Read official statement ↗
Important: Vendor backports can keep the displayed PHP version number unchanged; ask for the exact fixed build.
GoDaddy reports web hosting PHP patched; confirm the PHP build or build date on your specific site. No customer-side PHP upgrade required for these CVEs.
Independent verification; legacy-runtime review.
GoDaddy reports managed WordPress and Windows Hosting patched. Monitor further advisories; verify if you have unusual/custom PHP integrations.
Independent assurance and application smoke testing.
Update PHP via the OS or WHM/EasyApache 4, restart web workers and test the application; do not assume GoDaddy's shared-hosting rollout covers your VPS.
Authorized patch, rollback and validation.
Provider advisory: Read official statement ↗
Important: Cloud Armor managed rules are mitigating controls only; they do not replace PHP runtime updates.
Google says supported App Engine Standard runtimes receive automatic patched base images. Verify your application uses a supported runtime; upgrade old PHP.
Runtime inventory and modernization planning.
Google is rolling out patched base images where automatic updates are enabled. Verify your service's image and policy rather than assuming completion.
Verify deployment/automatic-update settings.
Google says flexible apps must redeploy, and custom images require rebuilding with patched PHP; disabled auto-update also requires redeploy.
Patch image, build and deploy safely.
Customer owns PHP installed in VMs and containers. Update OS/packages or image, restart or redeploy, and verify.
Cloud VM and Kubernetes remediation.
Provider advisory: Read official statement ↗
Important: Provider-specific scope is Webhosting and Managed Servers, not every Hetzner customer VM.
Hetzner reports 7.4 and 8.0–8.5 patched October 21, then 5.6 and 7.3 patched October 22, on managed infrastructure.
Confirm runtime and plan migration off older branches.
Hetzner notified cloud/dedicated clients but does not administer PHP inside self-managed servers. Apply approved vendor updates and verify.
Patch management and remediation evidence.
Provider advisory: Read official statement ↗
Important: Current advisory includes cPanel/Plesk and CloudLinux build details, not a blanket patched claim.
HostGator says remaining hosts are being updated with interim mitigations. Confirm the status of your individual server with support.
Independent patch-state verification and unresolved-risk analysis.
Review HostGator's patch tables, update the actual runtime using your panel or OS vendor, restart services and validate.
Authorized remediation and evidence report.
Provider advisory: Read official statement ↗
Important: Backported PHP builds can retain the older upstream version; inspect build date or package changelog.
hosting.com reports rollout completed across its hosting products and says customers need not act on its managed cPanel/Plesk offerings.
Independent assurance and application compatibility testing.
hosting.com says patches are installed for offered PHP 7.4+ builds. Check the panel and runtime used by each site.
Patch build and service verification.
Apply your OS, cPanel/Plesk or CloudLinux package updates and restart PHP; don't assume the provider did it inside your server.
Authorized patching and verified closure.
Provider advisory: Read official statement ↗
Important: Hostinger also posted guidance about a separate PHP CVE disclosed October 23; check its newest update.
Hostinger says all managed hosting servers were updated. hPanel PHP Info shows the Build Date, which can be newer even when the PHP version stays the same.
Independent verification or unsupported-PHP modernization.
Hostinger says VPS customers manage PHP. Apply supported OS/vendor fixes and verify every exposed web-serving runtime.
Patch execution and verification.
Provider advisory: Read official statement ↗
Important: InMotion also applied configuration mitigations; these do not substitute for completed PHP patch installation. The October 22 advisory distinguishes managed from self-managed servers.
InMotion says patched CloudLinux PHP builds are installed on all Shared, Reseller and WordPress hosting nodes. No customer-side PHP patch is required for these plans; verify legacy compatibility separately.
Independent patch/build verification and moving older sites to supported PHP.
InMotion says dedicated and UltraStack ONE servers were patched. Confirm your server uses the host-managed PHP packages rather than a custom installed runtime.
Runtime evidence, application smoke tests, and exception analysis.
InMotion reported most VPS patched and ongoing CWP 1.21 rollout and PHP rebuilds as of October 22. Verify the exact server and panel with InMotion support/status updates.
Confirm completion, identify runtime/panel exceptions and test applications.
InMotion explicitly directs self-managed root administrators to update PHP via EasyApache 4 or OS packages and restart Apache/PHP-FPM. Backed-up, authorized changes are required.
Scoped patch rollout, service restarts, validation and audit evidence.
Provider advisory: Read official statement ↗
Important: IONOS warned of phishing emails impersonating PHP security notifications; verify notices through its own portal.
IONOS states its provider-operated PHP services are patched. Verify if the site uses custom hosting outside those products.
Verification and legacy-PHP migration.
Install the appropriate PHP and OS security updates yourself, restart web-serving processes, and test the hosted apps.
Authorized inventory, patching and report.
Provider advisory: Read official statement ↗
Important: Kinsta posted a separate October 23 notice concerning CVE-2026-115560 and its mitigations.
Kinsta reports all sites protected and patched on October 22. It also maintains edge and local protections; no customer-side runtime patch was required.
Optional independent assessment, application test or future upgrade plan.
Provider advisory: Read official statement ↗
Important: The October 23 vendor statement provides package builds and suggests checking phpinfo; some published legacy rows contain apparent copy errors, so validate against the original vendor changelog.
Liquid Web lists available patched builds and is still deploying and verifying environments. Ask support whether your specific environment is complete.
Read-only verification, exception follow-up and application testing.
If you manage the OS/PHP packages, install the appropriate vendor builds through the panel or package manager, restart PHP and verify.
Scope, patch execution and validation.
Provider advisory: Read official statement ↗
Important: CloudLinux may backport patches without a PHP version-string change; follow Namecheap's October 23 build guidance.
Namecheap reports all PHP versions offered on shared hosting are patched, including older backported builds. No self-patching is needed on the shared platform.
Optional confirmation, compatibility or migration advice.
Namecheap explicitly instructs customers administering VPS/dedicated servers to apply PHP security updates themselves.
Authorized security update and verification.
Provider advisory: Read official statement ↗ Additional vendor guidance ↗
Important: OVHcloud's status page still notes extended maintenance even after the older-branch patches; check the live incident before assuming the window is over.
OVHcloud reports patched PHP 7.4–8.5 across clusters on October 21 and older 5.3–7.3 on October 23. Confirm your individual environment, especially during maintenance.
Independent verification or compatibility troubleshooting.
OVHcloud explicitly instructs root/VPS users to update PHP themselves. Patch OS or base image, restart web workers and test.
Automated host remediation and report.
Provider advisory: Read official statement ↗
Important: Pantheon also reported mitigations for a distinct October 23 PHP advisory.
Pantheon says updates to all customer PHP images completed by October 21 evening, with monitoring and network protections continuing.
Independent runtime/app verification if required.
Earlier status updates scheduled sandbox fixes over 24–48 hours; the later closure does not separately enumerate every free sandbox. Check your environment or ask Pantheon.
Check patch state for a specific sandbox.
Provider advisory: Read official statement ↗
Important: SiteGround also reports protective configuration measures for older available PHP versions; confirm any unusual version or override.
SiteGround says it controls PHP at the server layer and patched the supported versions. No customer patch action is requested.
Optional verification or legacy-version planning.
SiteGround's platform-wide statement includes managed hosting; verify the exact contract if you administer a separate custom PHP stack.
Custom-stack review if outside provider-managed scope.
Provider advisory: Read official statement ↗
Important: Source is an official October 22 company notice, not independent scanning of customer sites.
WP Engine says all its customer sites were patched after proactive mitigation. No customer action for these two PHP runtime CVEs.
Optional confidence check or non-PHP application work.
No matching hosting services. Clear filters or check the provider's official support channel.
These 20 providers are a research selection, not a verified market-share ranking. Status refers to a specific service category and to the provider's dated statement, not to any particular customer server. Independently installed PHP, custom images, old branches, and third-party packages may fall outside a host's managed coverage. Review the official notice before acting.
YOUR NEXT STEP
Version strings can be misleading: hosting vendors sometimes backport security fixes without changing PHP's headline version. Check the runtime actually serving requests, the vendor package/build or image digest, restart/redeployment state, and an application smoke test.
Never assume a firewall rule or mitigation alone is a complete PHP fix.
EDGAR TECH / PHP SECURITY
We help smaller development teams, MSPs and business owners verify actual PHP runtime patch state, implement approved fixes, and document the result. Start with a scoped conversation—not an unsolicited scan.