
How to update the PHP version in Plesk, cPanel and PrestaShop
How to check and update PHP in Plesk, cPanel and PrestaShop. Steps for each panel, a message for your host and checks for the website and SEO.

Check which PHP version your website uses, ask your hosting provider for the patch or apply it from the control panel. These are the steps for Plesk and cPanel, the precautions for PrestaShop and the checks to run before getting back to work.
To fix the PHP2Shell flaws, you have to update the server's PHP. Updating WordPress, PrestaShop or their plugins is not enough. If your hosting provider manages the server, start by asking them to confirm that they have installed the fix.
This guide explains how to check your version, update from Plesk or cPanel and make sure the website still works. If you are looking for an explanation of the flaws, it is in the news story about the two PHP security issues.
Check which PHP version your website uses
You can look it up without opening the server console:

Finding the PHP version in WordPress
- WordPress: Tools → Site Health → Info → Server. Look for “PHP version”.
- PrestaShop: Advanced Parameters → Information. The version appears in the server information.
Be careful: not every PrestaShop version supports every PHP version: - PrestaShop 1.6: Supports PHP 5.2 to 7.1 [It must be updated to a secure PrestaShop version or rely on other measures such as Cloudflare or extra protection from the hosting provider]
- PrestaShop 1.7: Supports PHP 5.4 to 7.4 [It must be updated to a secure PrestaShop version or rely on other measures such as Cloudflare or extra protection from the hosting provider]
- PrestaShop 8 (8.1.x): Supports PHP 7.2.5 to PHP 8.1 (PHP 8.1 recommended)
- PrestaShop 9 (9.0 / 9.1): Supports PHP 8.1 to PHP 8.3 / 8.5 (depending on the minor version, PHP 8.3 recommended)
- Plesk: Websites & Domains → choose the domain → PHP or PHP Settings.
- cPanel: Software → MultiPHP Manager. Some hosting providers use “Select PHP Version” instead.
Check each domain: two websites on the same hosting can use different versions. If the panel only shows “8.3” or “8.4”, ask the provider for the full version number and confirmation of the patch.
The official PHP advisory lists these versions, released on October 21, 2026:
| Version you use | Version with the fix |
|---|---|
| PHP 8.5 | 8.5.12 |
| PHP 8.4 | 8.4.27 |
| PHP 8.3 | 8.3.36 |
| PHP 8.2 | 8.2.35 |
| PHP 8.1 or earlier | No new official releases. Check whether your provider offers a patched package for the version you use. |
Some providers ship the fix without changing the main version number you see in the panel. A version lower than the one in the table needs to be checked with the hosting provider; on its own, it does not prove that it is still vulnerable.
Ask your hosting provider for the update
If you have shared or managed hosting, the provider normally installs PHP updates. You may be allowed to choose a version for your website, but that does not mean you can install the patch on the server.
Check their security notices. If there is no clear confirmation for your account, you can send this message to support:
Hello. I need to confirm that my websites are protected against the PHP flaws CVE-2026-109618 and CVE-2026-109619, known as PHP2Shell.
Which PHP version does each domain use? Have you installed the fix and restarted the necessary services?
If any website uses an old version, please tell me whether there is a patch from the provider or what change it needs. Before switching it to another PHP version, I need to check the website's compatibility.
If downtime is needed, please keep it short and have the server return a 503 status code to indicate that it is temporary. Thank you.
Keep the reply. If the provider has already applied the fix, skip to the checks at the end of this guide.
Prepare the PHP update
Updating within the same version and switching to another version are different operations. Going from PHP 8.3.35 to 8.3.36 installs a fix. Going from PHP 7.4 to 8.4 may require changes to the website, themes or modules.
- Make sure you have a recent backup of the files and the database, and that you know how to restore it.
- Write down which version each domain uses.
- If you are going to switch, for example, from PHP 8.1 to 8.4, check compatibility and test it first on a copy of the website.
- Make the change when you can check the result and support is available in case something fails.
If the current version has a patched and compatible update, you do not need to use this intervention to also change your WordPress, PrestaShop or theme version.
Update the PHP version in Plesk
In Plesk there are two tasks: installing the available updates on the server and checking which PHP each domain uses. The first one requires administrator permissions. If you do not see “Tools & Settings”, ask your hosting provider to do it.

You can choose the PHP settings in your Plesk
Install the update on the server
- Go to Tools & Settings → Updates. The Plesk installer will open.
- Open Update Components or “Product component updates”, depending on the panel language.
- Review the PHP versions with available updates and click Continue.
- Wait for it to finish and check that there are no errors. Review the installed versions in Tools & Settings → Plesk Components.
- Confirm that the PHP services your websites use have been restarted. If you do not know how to check it, ask the administrator.

Updating with Plesk
The process is described in the Plesk updates documentation. It has been tested and carried out successfully.
Choose the version each domain uses
- Go to Websites & Domains and select the website.
- Open PHP or PHP Settings.
- Check the selected version. If you need to change it, choose one that includes the fix and is compatible with your website.
- Save the change and test the website. Repeat the check on the other domains.
If the version you need is missing, the administrator will have to install it. You can read about the selector in the Plesk PHP settings help.
Update the PHP version in cPanel
cPanel lets you choose the version for a website; WHM lets you manage the server. If you only have cPanel, start by asking the provider to confirm that the available versions include the fix.
Change a domain's version from cPanel

PHP in Plesk
- Open Software → MultiPHP Manager.
- Select the domain you want to review.
- If you need to change it, choose a compatible version that the provider has confirmed as patched.
- Click Apply and check the website.
These steps apply to MultiPHP Manager. If your panel shows “Select PHP Version”, follow your hosting provider's instructions: it is a different selector.
Install the update from WHM
This section is for whoever manages the server.
- Check that the provider of the PHP packages has already released the fix.
- Go to Software → System Update. This tool updates the server packages, not just PHP. If you only need to update PHP, the administrator must do it in the way that applies to their system.
- After installing it, restart the service that runs PHP. If you use PHP-FPM, it is under Restart Services → PHP-FPM Service for Apache, according to the cPanel documentation. Other setups may require restarting Apache or another service.
- Check in Software → MultiPHP Manager which version each domain uses and confirm that they all use patched packages.
If the server uses CloudLinux and its PHP selector, also check the versions managed by that selector. Updating one PHP installation does not guarantee that the others are up to date.
Update PHP if your shop uses PrestaShop
PHP is updated from the hosting or the server, not from the PrestaShop panel. Before switching versions, check that it is compatible with your shop version, theme and modules.
- Check the current version in Advanced Parameters → Information.
- Ask your hosting provider to confirm whether that version has the fix.
- If you need to move to another PHP version, test a copy of the shop first.
- After the change, check access to the back office, product pages, the cart and the checkout process.
For older shops, PrestaShop recommends asking for a patched package for the PHP version they already use. A full shop migration needs its own preparation; it is not something to improvise in response to this emergency.
Temporarily take the website offline during the update
Ask the administrator whether it needs to go offline. If there is downtime, prepare a maintenance notice served by the hosting or the CDN, without relying on PHP. Activating a maintenance plugin does not block these attacks, because they can happen before the application runs.
For a short interruption, Google recommends responding with a 503 status code. That code indicates that the website is temporarily unavailable. It does not guarantee you will keep your rankings if the downtime drags on.
- 503 during the downtime: do not return a 404, which indicates that the page does not exist, or a 200 with the same notice on every page.
- Retry-After: this header lets you tell the crawler when it can try again. It is a hint, not a guaranteed appointment.
- Accessible robots.txt: keep its normal response and do not add a blanket block to carry out the maintenance.
- Short downtime: Google intends the 503 for closures of one or two days. A longer interruption can affect indexing.
If you do not manage the server, pass these instructions on to your hosting provider. You do not need to modify configuration files to ask for downtime done properly. To learn more, see the articles on status codes and SEO and using 503 and Retry-After.
What to do if you cannot update yet
Ask the provider how they are going to protect the server and when the fix will be available. According to the PHP team, temporary measures only block some forms of attack; the complete solution is to install the update.
Cloudflare or another web application firewall can add protection, but they do not replace the patch. Blocking forms or uploads can also prevent payments, user sign-ups or imports: any temporary measure should be reviewed by whoever manages the server. If they cannot keep it protected, they will have to consider isolating it until it is updated.
Check the website after updating PHP
- Confirm the version and the patch. Review each domain and ask the administrator to confirm that the necessary services have been restarted.
- Test several pages. Open the homepage, a category, a product page or article, and the admin panel. Also check forms, uploads and, if there is a shop, a test purchase.
- Remove the maintenance mode. Check that the pages show their content again and respond normally. Remove any temporary blocks that are no longer needed.
- Check Search Console. In Settings → Crawl stats, see whether server errors persist. The reports are not updated instantly.
- Ask for a security review if there was exposure. Installing the patch does not remove an earlier intrusion. If unknown files, users or tasks appear, ask the person in charge of the technical side to investigate and keep the logs.
References
- (PrestaShop), K. P. (2026, October 21). Critical PHP security updates: what PrestaShop users need to know. build.prestashop-project.org. https://build.prestashop-project.org/news/2026/php-security-updates-october-2026/ (“Top priority for every merchant”; PS 9 = PHP 8.1–8.5; Advanced Parameters › Information)
- (SEJ), V. P. (2026, October 21). Critical PHP Core Security Flaws Affect Websites, Including WordPress. Search Engine Journal. https://www.searchenginejournal.com/critical-php-core-security-flaws-affect-websites-including-wordpress/593812/ (Site Health in WordPress; Dutch and Finnish public websites taken offline)
- Automattic (2026, October 21). Your Sites Are Protected Against the PHP2Shell Vulnerabilities. automattic.com. https://automattic.com/2026/10/21/your-sites-are-protected-against-the-php2shell-vulnerabilities/ (WordPress.com, VIP, WP Cloud, Pressable and Tumblr already protected; “nothing you need to do”; everyone else should ask their provider for confirmation)
- Barry Schwartz (Search Engine Roundtable) (2026, October 21). Google Advice On Taking Sites Down When Fixing PHP2Shell. Search Engine Roundtable. https://www.seroundtable.com/google-php2shell-42353.html (Covers John Mueller's post)
- Central, G. S. (2011, January 26). How to deal with planned site downtime. Google Search Central. https://developers.google.com/search/blog/2011/01/how-to-deal-with-planned-site-downtime (Linked by Mueller: 503 + Retry-After for planned downtime)
- Central, G. S. (2025, December 10). Pause or disable your online business. Google Search Central. https://developers.google.com/search/docs/crawling-indexing/pause-online-business (Linked by Mueller: 503 for days only, Retry-After, no 404/410/403/noindex, static homepage with 200)
- Central, G. S. (2026, February 4). How HTTP status codes and network errors affect Google Search. Google Search Central. https://developers.google.com/search/docs/crawling-indexing/http-network-errors (5xx: content ignored, URLs kept and then removed; 429 treated as overload; 4xx removes; soft 404 with 200)
- Central, G. S. (2026, October 6). Reduce the Googlebot crawl rate. Google Search Central. https://developers.google.com/search/docs/crawling-indexing/reduce-crawl-rate (Emergency section: 500/503/429, Retry-After, 1-2 days at most; updated on 6-10-2026)
- CISA (2026, October 21). Critical Vulnerabilities in PHP Require Immediate Patching. cisa.gov. https://www.cisa.gov/news-events/alerts/2026/10/21/critical-vulnerabilities-php-require-immediate-patching (Patch now; unpatched or on 8.1 or lower, take offline; WAF as a layer; watch for workers spawning shells)
- Cloudflare (2026, October 21). Cloudflare deploys protections against php2shell vulnerability. Cloudflare. https://blog.cloudflare.com/php-vulnerabilities-waf-protection (Rules since 03:02 UTC on all plans with WAF (Free included); check block mode on paid plans; patching is still needed)
- CloudLinux (2026, October 21). Imunify360 Ruleset 8.83 Blocks the Public Exploit Shape. blog.cloudlinux.com. https://blog.cloudlinux.com/php-cve-2026-109618-and-cve-2026-109619 (ea-php and alt-php after the official release; ruleset 8.83)
- cPanel (2026, October 21). How to log in to your server or account. docs.cpanel.net. https://docs.cpanel.net/knowledge-base/accounts/how-to-log-in-to-your-server-or-account/ (cPanel on port 2083, WHM on 2087, cpsess token in the URL)
- cPanel (n.d.). MultiPHP Manager for cPanel. docs.cpanel.net. https://docs.cpanel.net/cpanel/software/multiphp-manager-for-cpanel/ (Selecting a domain's PHP version.)
- cPanel (n.d.). Restart Services. docs.cpanel.net. https://docs.cpanel.net/whm/restart-services/restart-services/ (Restarting PHP-FPM from WHM.)
- cPanel (n.d.). System Update. docs.cpanel.net. https://docs.cpanel.net/whm/software/system-update/ (Updating server packages from WHM.)
- CybaVerse (2026, October 21). PHP2Shell: Check Exposure and Hunt for Compromise. cybaverse.co.uk. https://www.cybaverse.co.uk/en/php2shell-checker (Behavioural indicators of compromise)
- PHP Team (2026, October 21). Security advisory: Critical remote code execution vulnerabilities, update now. PHP. https://www.php.net/archive/2026.php#2026-10-21-5 Main source
- Dive, C. (2026, October 21). Critical PHP vulnerabilities expose most websites to potential compromise. cybersecuritydive.com. https://www.cybersecuritydive.com/news/php-website-vulnerabilities/833580/ (Talos: half of exposed instances on unpatched versions; agencies call for shutdowns)
- Escudero, D. (2026, October 21). PHP2Shell: PrestaShop 1.6, 1.7 y 8, sin parche oficial. davidescudero.com. https://davidescudero.com/vulnerabilidad-php-prestashop-php2shell/ (PrestaShop/PHP table; secondary source, not cited in the text)
- Geniar, M. (2026, October 21). PHP CVE-2026-109618 and CVE-2026-109619: how to apply the patches. ma.ttias.be. https://ma.ttias.be/php-cve-2026-109618-patch/ (apt/dnf commands, package versions per distro, checking for old processes)
- Huntress (2026, October 21). Rapid Response: php2shell. huntress.com. https://www.huntress.com/blog/php2shell-leaked-critical-php-vulnerabilities (Publication time, root cause, behavioural indicators)
- Labs, M. (2026, October 21). PHP2Shell: Why websites are going offline for emergency security updates. malwarebytes.com. https://www.malwarebytes.com/blog/bugs/2026/10/php2shell-why-websites-are-going-offline-for-emergency-security-updates (Preventive shutdowns, not a sign of a breach; advice for owners and visitors)
- Mueller, J. (2026, October 21). John Mueller's post. Bluesky. https://bsky.app/profile/johnmu.com/post/3myfhjovzvk27 (503 instead of timeouts/404/500, outside PHP)
- NCSC-NL (2026, October 21). php2shell operational information. GitHub. https://github.com/NCSC-NL/php2shell (Mitigations and further reading)
- Patchstack (2026, October 21). Major security alert: PHP vulnerable to critical RCE, attacks ongoing. patchstack.com. https://patchstack.com/articles/php-major-vulnerability-alert-10-2026/ (Exploitation timeline (07:34 UTC), Dutch websites taken offline via NOS, advice for WordPress)
- PHP (2026, October 21). CVE-2026-109618 (OOM corruption). GitHub. https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w (CVE advisory)
- PHP (2026, October 21). CVE-2026-109619 (stale global state). GitHub. https://github.com/php/php-src/security/advisories/GHSA-6wmf-4rv5-p3rp (CVE advisory)
- PHP (2026, October 21). Security advisory: Critical remote code execution vulnerabilities, update now. php.net. https://www.php.net/archive/2026.php#2026-10-21-5 (Primary source: patched versions, SAPIs at risk, mod_php, mitigations)
- Plesk (2026, October 21). How to log in to Plesk. support.plesk.com. https://support.plesk.com/hc/en-us/articles/12377667582743-How-to-log-in-to-Plesk (Access via https://host:8443)
- Plesk (2026, October 21). Vulnerability CVE-2026-109618 and CVE-2026-109619: Remote code execution in PHP shipped with Plesk. support.plesk.com. https://support.plesk.com/hc/en-us/articles/44397729587351-Vulnerability-CVE-2026-109618-and-CVE-2026-109619-Remote-code-execution-in-PHP-shipped-with-Plesk (8.2–8.5 packages released; 8.1/8.0/7.4 in development. Returned a 403 to the bot: read through the search engine summary)
- Plesk (n.d.). PHP Settings. docs.plesk.com. https://docs.plesk.com/en-US/obsidian/customer-guide/websites-and-domains/hosting-settings/php-settings.70742/ (PHP selection per domain and compatibility.)
- Plesk (n.d.). Plesk Updates. docs.plesk.com. https://docs.plesk.com/en-US/obsidian/administrator-guide/plesk-updates-and-upgrades.59215/ (Installing updates from Tools & Settings.)
- Record, T. (2026, October 21). Hundreds of websites taken offline as concern grows over two PHP vulnerabilities. therecord.media. https://therecord.media/php-script-vulnerabilities-warnings (Nintendo, Charité, OBS, Finland; agency warnings)
- Register, T. (2026, October 21). PHP devs publish critical bug fix as site owners warned. theregister.com. https://www.theregister.com/security/2026/10/21/php-devs-publish-critical-bug-fix-as-site-owners-warned-pull-em-offline-if-youre-unpatched/5304519 (CERT-EU: isolate exposed systems; noyb, Dutch Parliament, Finland)
- Sánchez, C. (2026, March 2). Códigos de respuesta desde el servidor en el SEO. sanchezdonate.net. https://sanchezdonate.net/articulo/codigos-de-respuesta/ (Linked reference: codes by family and how Google reads them)
- Sánchez, C. (2026, October 8). Reduce Google's crawling of our website. sanchezdonate.net. https://sanchezdonate.net/en/article/reduce-googles-crawling-of-our-website/ (Linked reference: 503/429 and Retry-After, how to send it in Apache, LiteSpeed and nginx)
- Sansec (2026, October 21). PHP2Shell: Critical PHP RCE (CVE-2026-109618, CVE-2026-109619). sansec.io. https://sansec.io/research/php2shell (multipart/form-data vector, nginx/Apache mitigations, confirmed apps)
- Tenable (2026, October 21). php2shell FAQ. tenable.com. https://www.tenable.com/blog/php2shell-cve-2026-109618-cve-2026-109619-frequently-asked-questions-about-critical-php-remote (Cloudflare sees the first attacks; “ini settings won’t save you”)
- Unit 42 (Palo Alto Networks) (2026, October 21). CVE-2026-109618 and CVE-2026-109619. unit42.paloaltonetworks.com. https://unit42.paloaltonetworks.com/cve-2026-109618-cve-2026-109619/ (More than 22.6 million exposed instances (own telemetry, no methodology))
- W3Techs (2026, October 21). Usage statistics and market share of PHP for websites. w3techs.com. https://w3techs.com/technologies/details/pl-php (69.3% of websites with a known server-side language; v8 65.2%, v7 27%, v5 7.7%)
- WooCommerce (n.d.). How to update your PHP version. woocommerce.com. https://woocommerce.com/document/how-to-update-your-php-version/ (Checking the PHP version from WordPress Site Health.)
I currently offer advanced SEO training in Spanish. Would you like me to create an English version? Let me know!
Tell me you're interested



