Skip to content
Skip to content
Digitalized Planet

How to update the PHP version on your hosting

The October 2026 PHP flaws are fixed by updating PHP on the server, not WordPress. On shared hosting that is a setting or a request to your host; on your own server it is a package update. Here is how, safely.

USD 750 once, USD 79 a month. No PHP, no plugins, nothing for you to update.

Last updated October 22, 2026

Shared hosting: change it in the control panel

  1. Make a full backup of the files and the database first, and download it.
  2. cPanel: open MultiPHP Manager, tick your domain and pick the newer version (cPanel's guide). Plesk: open the domain's PHP settings and pick the version.
  3. Pick a supported line your site works with. WordPress recommends 8.3 or newer.
  4. Open your site and its admin, click through the main pages and the contact form. If something breaks, switch back and tell whoever built the site.

Picking a newer line, say 8.3, only helps if your host's 8.3 is the fixed release (8.3.36) or carries the fix. Ask.

What to ask your host

  • "Is the PHP serving my site patched against CVE-2026-109618 and CVE-2026-109619, and since when?"
  • "Which PHP versions can I choose, and which are fixed?"
  • "If my site needs PHP 8.1 or older, do you provide a backported fix?"

Your own server

Update to PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or install your distribution's updated packages, then restart PHP-FPM, Apache or your PHP server so every worker runs the new code. PHP says Linux distributions and long-term support vendors got the patches in advance. PHP 8.1 and older get no update from PHP; it published minimal source backports for 7.4, 8.0 and 8.1 (PHP's advisory).

If you cannot update today

PHP lists settings that reduce exposure to the known attack paths. It is clear that they do not make a server safe and only an update does:

  • Set session.upload_progress.enabled to 0 in php.ini or the FPM pool, not through ini_set() or .user.ini, and restart every worker.
  • Set memory_limit to -1 where applications cannot override it, such as php_admin_value in the FPM pool or Apache configuration.
  • Set a low post_max_size: 8M for sites without uploads, 32M with uploads, and keep upload_max_filesize below it.
  • On PHP 8.5, set fatal_error_backtraces to 0 and restart every worker.
  • Limit request size, field count and header count at the web server or proxy, including requests without a Content-Length.

Will you have to do this again?

Yes. Each PHP line gets security fixes for a limited time: 8.2 until 31 December 2026, 8.3 until 31 December 2027, 8.4 until 31 December 2028 (supported versions). Then the site has to move again, and its plugins with it. If that is not how you want to spend your time: a website without maintenance.

Done with PHP updates?

We rebuild your site as fast pages with nothing on the server for you to patch, and you still edit it from your phone.

Rebuild my website

Written with AI help; facts from cpanel.net, php.net; checked October 22, 2026.