PHP Vulnerability Responses by Company

Reclaim Hosting

Global hosting
Aliases / services
Reclaim Hosting / reclaimhosting.com / Reclaim Cloud / Domain of One's Own
Official website
https://www.reclaimhosting.com/

Each response applies only to its stated service scope. “Not listed” does not mean unpatched or unaffected.

Response status by service

Reclaim Cloud (self-managed PHP containers)

Response status
Customer update required
Response information checked
2026-10-27

Current re-audit: Official response verified · Research date: 2026-10-27

The 22 October notice requires redeployment of self-managed containers to fixed releases by 27 October.

Scope: Managed Hosting is separate. Planned provider updates after the deadline are not completion evidence.

What users should do

Check application compatibility and redeploy a fixed release. Redeploying an old release does not fix it.

Official service URL

Source URLs

  1. Reclaim Cloud PHP2Shell responsehttps://blog.reclaimhosting.com/reclaim-cloud-and-php2shell/Response evidence
  2. https://blog.reclaimhosting.com/https://blog.reclaimhosting.com/Response evidence
  3. https://blog.reclaimhosting.com/php2shell-vulnerability/https://blog.reclaimhosting.com/php2shell-vulnerability/Response evidence
  4. https://blog.reclaimhosting.com/domain-of-ones-own-v2-migrations-and-the-php2shell-security-vulnerability/https://blog.reclaimhosting.com/domain-of-ones-own-v2-migrations-and-the-php2shell-security-vulnerability/Response evidence

Reclaim Managed Hosting

Response status
Managed environments patched
Response information checked
2026-10-27

Current re-audit: Official response verified · Research date: 2026-10-27

On 22 October, all Managed Hosting environments, including those on Cloud, were reported patched.

Scope: This completion does not cover self-managed Cloud, Shared or EDU.

What users should do

Check application compatibility where PHP 8.1 was upgraded to 8.2.

Source URLs

  1. Reclaim Cloud PHP2Shell responsehttps://blog.reclaimhosting.com/reclaim-cloud-and-php2shell/Response evidence

Reclaim Shared Hosting

Response status
Mitigation and update rollout announced
Response information checked
2026-10-27

Current re-audit: Official response verified · Research date: 2026-10-27

The 21 October notice describes temporary mitigation and PHP patch rollout.

Scope: No later service-specific completion notice was found in this review.

What users should do

Ask support to confirm completion and required actions for your environment.

Source URLs

  1. https://blog.reclaimhosting.com/php2shell-vulnerability/https://blog.reclaimhosting.com/php2shell-vulnerability/Response evidence

ReclaimEDU

Response status
Mitigation and update rollout announced
Response information checked
2026-10-27

Current re-audit: Official response verified · Research date: 2026-10-27

The 21 October notice describes temporary mitigation and PHP patch rollout.

Scope: No later service-specific completion notice was found in this review.

What users should do

Ask support to confirm completion and required actions for your environment.

Source URLs

  1. https://blog.reclaimhosting.com/php2shell-vulnerability/https://blog.reclaimhosting.com/php2shell-vulnerability/Response evidence

Domain of One's Own

Response status
Eligible migrations and exceptions documented
Response information checked
2026-10-27

Current re-audit: Official response verified · Research date: 2026-10-27

The notice reports eligible institutions migrated to v2, with old PHP removed and 8.2 as default.

Scope: This is not universal patch-completion evidence for every institution.

What users should do

Confirm your institution's migration; coordinate WHMCS and other dependencies individually.

Source URLs

  1. https://blog.reclaimhosting.com/domain-of-ones-own-v2-migrations-and-the-php2shell-security-vulnerability/https://blog.reclaimhosting.com/domain-of-ones-own-v2-migrations-and-the-php2shell-security-vulnerability/Response evidence
Related official sources
  1. Reclaim Cloud PHP2Shell responseOfficial noticeOfficial guidance on this vulnerability and the scope of the response.

Comments