How to Check Your PHP Version (cPanel, WordPress, CLI) and Whether It Is Safe

What is the quickest way to check your PHP version?

The quickest way to check your PHP version depends on your access. With SSH, run php -v. On WordPress, open Tools, then Site Health, then the Info tab and expand Server. On shared hosting, open the PHP version selector in cPanel or Plesk. Each method takes under a minute.

Write down the full version, such as 8.3.36, not just 8.3. The last number tells you whether the latest security patch is installed.

Which PHP versions are safe in 2026?

Safe PHP versions are those still inside official security support and patched for PHP2Shell: 8.5.12, 8.4.27, 8.3.36 and 8.2.35 or later. PHP 8.1 and older are end of life and get no official fixes. PHP 8.2 is safe until 31 December 2026, after which it stops receiving security updates.

For a new project or an upgrade, choose PHP 8.4 or 8.5. They have the longest support windows, and most WordPress plugins and current Laravel and Symfony releases support them. Our PHP end-of-life guide explains the support dates in detail.

How do you check the PHP version in cPanel or Plesk?

In cPanel, log in and open Select PHP Version or MultiPHP Manager under Software. The current version is shown at the top, or per domain in MultiPHP Manager. In Plesk, open Websites & Domains, then PHP Settings for the domain. The version and handler (for example FPM) are listed there.

Hosting panels often show only the branch, such as 8.3. To see the exact patch release, use WordPress Site Health or a temporary phpinfo() file, both covered below.

How do you check the PHP version in WordPress?

In WordPress, go to Tools, then Site Health, then the Info tab, and expand the Server section. The PHP version line shows the exact version the website runs. Site Health also warns you on the Status tab when your PHP version is outdated.

This is the most reliable check for WordPress, because it shows the PHP the web server actually uses, not the command-line PHP.

How do you check the PHP version from the command line?

From the command line, run php -v. The first line shows the version, for example PHP 8.4.27 (cli). Run php-fpm -v, or the versioned command such as php-fpm8.4 -v, to see the version the web server uses through PHP-FPM.

Servers often have several PHP versions installed. The command-line default can be 8.4 while a site still runs 8.1 through its FPM pool, so always check the web version too.

How do you check the PHP version with phpinfo()?

Create a file named with a random name, such as check-8f3a.php, containing <?php phpinfo(); and upload it to your site’s web root. Open it in a browser and read the version at the top of the page. Then delete the file immediately, because it shows server paths and settings attackers can use.

How do you check the PHP version in Laravel, Composer or Docker?

In Laravel, run php artisan about to see the PHP and Laravel versions together. Check composer.json for the require.php constraint, which tells you which PHP versions the project is meant to support. In Docker, run docker exec <container> php -v, or read the FROM line of the Dockerfile, such as php:8.3-fpm.

A Dockerfile that pins only the branch, such as 8.3-fpm, picks up patch releases when you rebuild the image. A running container does not update itself, so rebuild and redeploy after a security release.

What should you do if your PHP version is not safe?

If your PHP version is not safe, first update to the latest patch release on your branch, such as 8.3.36. If your branch is end of life, plan an upgrade to PHP 8.4 or 8.5, test the site on a staging copy, then switch. If anything looks wrong after PHP2Shell, check the site for signs of compromise.

Old applications written for PHP 5 or 7 usually need code changes before they run on PHP 8. Our guide to upgrading PHP 5 and 7 applications covers the common breaking changes and how long an upgrade takes.

• 1. Note the exact PHP version and where you found it.
• 2. Compare it with the table above.
• 3. Update to the latest patch on your branch today.
• 4. If the branch is end of life, schedule an upgrade to PHP 8.4 or 8.5.
• 5. Test forms, logins and checkout on staging before switching the live site.