To confirm whether Pressidium applied a PHP security patch or a named CVE (Common Vulnerabilities and Exposures), start with the PHP version the site runs.

Switching that version in the Dashboard is not the same as applying a security fix to the version already in use.

This article is for Pressidium Managed WordPress Hosting. It does not describe Pressidium EDGE PHP runtimes.

CVE-2026-115560 is handled with a server configuration change on those same versions, not a PHP patch.

These are platform actions. You do not receive them by switching PHP version in the Dashboard. Confirm your PHP version in the steps below. For site-specific confirmation, open a Support request and include the CVE IDs.

Version switch versus security patches

You switch PHP version for a website and environment from the Dashboard. That change selects a different PHP runtime for Production or Staging. Follow Switch your PHP runtime.

A security patch on the PHP version you already run is a platform action. The Dashboard does not list CVE status. See the October 2026 note above for named CVEs.

Pressidium does not apply every published PHP update on the day it ships. All PHP versions are upgraded every two to three months. Critical vulnerabilities are patched as soon as possible.

Who owns what

You choose the PHP version for each website and environment, test the change, and keep themes and plugins compatible with the version you select.

Pressidium applies security patches on the version you already run, on the cadence above. Pressidium also evaluates php.ini override requests and disabled PHP function exceptions. Those are Support-reviewed configuration requests. You cannot install a custom PHP binary.

Support confirms named CVEs that are not covered by a current note on this page, and can confirm site-specific status. You cannot check this in the Dashboard.

Supported versus legacy or EOL PHP

Pressidium’s PHP version support follows the minimum PHP version WordPress supports.

PHP versions older than 8 are end of life on php.net (PHP: Supported Versions). Upgrading PHP recommends at least PHP 8.1.x. The PHP Engine menu lists the versions available for the site. The current latest version is PHP 8.4.

When a PHP version reaches end of life, Pressidium removes it from the versions you can choose when you create a new website. Existing websites that already run that version keep it until you switch.

Switching PHP can affect themes and plugins.

Confirm the PHP version on production and staging

Pressidium can run different PHP versions per website and environment. Check both Production and Staging.

PHP Engine shows the minor version (for example 8.4). It does not show the exact version (for example 8.4.12).

Minor version in the Dashboard

  1. In the sidebar, open Websites. That opens Websites overview. Select the website.

  2. In the navigation bar, select Production or Staging.

  3. Open Settings.

  4. Check the version in PHP Engine.

Exact version

To see the exact PHP version (for example 8.4.12), use one of these methods on the environment you are checking.

phpinfo()

  1. Create a PHP file whose only contents are:

    <?php phpinfo(); ?>

  2. Open that file in the browser for the same environment (Production or Staging).

  3. Read the exact PHP version at the top of the page.

SSH

  1. SSH to the website for that environment.

  2. Run php -v. The first line shows the exact PHP version for that environment.

For SSH access, follow Managing SSH Access.

Plugin notices that tell you to update PHP

A plugin may show a notice in WordPress Admin that tells you to update PHP. That notice is not from Pressidium. Confirm the version in PHP Engine. Follow Upgrading PHP for compatibility work before you switch. Do not switch production only because a plugin showed that notice.

When to contact Support

Open a Support request when you need any of the following:

  • Confirmation for a named CVE that is not in the October 2026 note

  • Site-specific confirmation for a CVE that is in that note

  • A php.ini override

  • An exception for a disabled PHP function

  • Help after a PHP version switch that broke the site

Include the website, the PHP Engine minor versions for Production and Staging, the exact version from phpinfo or php -v if you have it, the CVE identifier if you have one, and what you observed.

Where to go next