Website support日本語Contact →

TSUMIRA JAPAN · PRACTICAL GUIDES

Plesk PHP security updates: builds, backports and the panel

Information reviewed: · Published by Tsumira Japan (SourceArt Ltd)

Review website PHP and Plesk’s own sw-engine separately. Some Plesk fixes for PHP 7.4, 8.0 and 8.1 retain their upstream version, so build information and the exact supplier package matter.

Match the official correction to your package

ComponentPlesk correction reviewed 22 October 2026
PHP 8.2 / 8.3 / 8.4 / 8.58.2.35 / 8.3.36 / 8.4.27 / 8.5.12
Linux PHP 7.4 / 8.0 / 8.17.4.33 / 8.0.30 / 8.1.34 built on 21 October 2026
Panel sw-engine18.0.81 Update 4 or 18.0.80 Update 11

These are Plesk’s conditions, not a blanket assessment of other vendors or custom builds. Match the installed supplier, full package release and build information.

Installed PHP and assigned PHP are different facts

A fixed runtime can exist on disk while a domain still uses another handler. Map the target domain to its PHP setting and FPM pool.

An administrator should also confirm that the associated running processes use the updated binary. Keep panel, CLI and domain configuration evidence distinct.

Unchanged legacy version numbers need package evidence

An old build and a corrected rebuild may both display 7.4.33. A public header often omits the build evidence needed to distinguish them.

A correction for these CVEs does not restore upstream support for an end-of-life branch. Review the maintenance conditions and migration plan separately.

Record panel and website remediation separately

Updating the panel does not establish that every website PHP handler is corrected. Updating website PHP likewise does not confirm the panel runtime.

Agree backups, package scope, service impact and functional checks before maintenance. A bulk branch switch can break applications and needs compatibility review.

Questions and answers

Does a working panel login prove remediation?

No. Compare panel and website PHP against their respective correction conditions.

Does the PHP 7.4 correction apply to PHP 7.3?

No. Check support from the supplier and plan the applicable remediation or compatible migration.

Can the public checker obtain the build date?

Not when it is absent from the public response. Use installed package and administrative evidence.

Official references

Official guidance and interfaces can change. Confirm your actual plan, configuration and the supplier’s latest notice. This guide does not certify the security or patch status of any individual environment.

Need help with your site?

We can help clarify the information and scope. Paid work begins after you approve the scope and cost.

Meet Tsumira developer Steve vom Wege · Tsumira.jp ↗