Is PHP2Shell fixed on GoDaddy?

Status as of October 26, 2026: GoDaddy reports patching PHP on its managed plans (partly confirmed in two of its own documents).

The short answer

GoDaddy reports patching all PHP versions (Oct 21–22, 2026): Managed Hosting for WordPress, Web Hosting, Windows Hosting. VPS: not patched by GoDaddy; customers update PHP themselves. We found two of the host’s own documents saying so. A host’s statement covers its managed platform, not a server you run yourself (source: GoDaddy). A fixed package only counts once it’s installed and PHP has restarted (source: AlmaLinux). A related flaw, CVE-2026-115560, has no fix in any PHP release as of October 23, 2026 (source: php.net advisory on CVE-2026-115560, October 23, 2026).

Fix status on GoDaddy

How to check on GoDaddy (read-only)

GoDaddy’s own test is the PHP build date: October 21, 2026 or later. You can see it in a temporary phpinfo() page (delete it straight afterwards) or ask GoDaddy support. On a VPS, check the server itself.

If someone else runs your server, ask them in writing: the questions and a copy-ready email. If it’s your own VPS or server, nobody patches PHP for you; check it with the steps for your Linux distribution in the status table. (source (source: GoDaddy))

CVE-2026-115560

On October 23, 2026, PHP disclosed a related flaw, CVE-2026-115560, that the October 21 releases don’t fix. Until its next regular bugfix release, PHP recommends turning off session upload progress (session.upload_progress.enabled=0) in the server configuration and restarting PHP. Setting it from application code (ini_set()) or a per-directory .user.ini file doesn’t count (source: php.net advisory on CVE-2026-115560, October 23, 2026).

On GoDaddy: GoDaddy’s article (update of October 23, 2026) says CVE-2026-115560 isn’t patched in PHP yet, and that session.upload_progress.enabled = 0 has been in place on its managed servers. VPS customers should set it in php.ini and restart PHP. (GoDaddy)

Notes for GoDaddy

• GoDaddy says its patched builds keep the previous version number: a site can show 8.5.11 and include the fix. GoDaddy’s check is a PHP build date of October 21, 2026 or later.
• Your host may have patched PHP: GoDaddy said it did. Ask for written confirmation for your account (source: GoDaddy).

Sources (checked October 26, 2026)

• GoDaddy: Status: PHP Vulnerability Information. Page date: latest entry Oct 22, 2026 21:06 UTC (Monitoring). States: Patched managed services, including Web Hosting and Managed Hosting for WordPress.
• GoDaddy: Important PHP security update: what website owners need to do. Page date: shown as Oct 20, 2026; latest update Oct 23, 2026 21:00 UTC. States: Patched all PHP versions on Managed Hosting for WordPress, Windows Hosting and Web Hosting; VPS customers update PHP themselves; builds keep the previous version number, check for a build date of Oct 21, 2026 or later; CVE-2026-115560 not yet patched, session.upload_progress.enabled = 0 in place on its managed servers.

Upstream facts (fixed releases, CVE-2026-115560, end-of-life dates) are footnoted to /sources. We list a build as confirmed only when two different primary documents state it. Method.

Related

Hostinger · SiteGround · WP Engine · All platforms · How to prove your server is patched · What to ask your host or developer

Want it checked for you?

• Patch Verification & Compromise Review. Collection is read-only, and we change nothing on your server. You get a plain-English report: where each fix stands, as of a stated time, plus a compromise review from October 17, signed by the Approver of Record. Ask for it
• Check it yourself, free. The read-only steps are on our PHP2Shell page. Our open-source self-check script is publishing soon.