{"id":3448,"date":"2026-10-21T18:09:01","date_gmt":"2026-10-21T16:09:01","guid":{"rendered":"https:\/\/www.panelalpha.com\/blog\/?p=3448"},"modified":"2026-10-21T21:01:13","modified_gmt":"2026-10-21T19:01:13","slug":"php-vulnerabilities-panelalpha-security-update","status":"publish","type":"post","link":"https:\/\/www.panelalpha.com\/blog\/php-vulnerabilities-panelalpha-security-update\/","title":{"rendered":"PanelAlpha security updates released following critical PHP vulnerabilities"},"content":{"rendered":"
\n

Two serious vulnerabilities in PHP, each rated 9.2 out of 10<\/strong> under CVSS v4.0, have prompted urgent security updates across the PHP ecosystem. As soon as the fixes became available, our team got to work incorporating them into PanelAlpha and testing the updated builds. PanelAlpha v1.9.8.3 is now available, along with security updates for both supported generations of PanelAlpha Engine<\/strong>.<\/p>\n

We know how important it is to keep the services you manage secure, especially when news like this breaks. Our priority was to get the updated versions into your hands as quickly as we could, while making sure they were ready to use. We recommend updating as soon as possible.<\/strong><\/p>\n

These vulnerabilities affect PHP itself, rather than a flaw specific to PanelAlpha or its WHMCS integration. Still, PHP can run in several different parts of your setup, so it is important to update each relevant component.<\/p>\n<\/div>\n\n

\n\n
\n\n
\n

The PHP vulnerabilities, in brief<\/h3>\n\n

Two critical vulnerabilities that can allow unauthenticated remote code execution on affected PHP servers.<\/p>\n <\/div>\n\n

\n

CVSS v4.0<\/p>\n\n

9.2<\/span> \/ 10<\/span><\/p>\n\n

Vulnerability<\/p>\n <\/div>\n\n <\/div>\n\n

\n\n
\n

CVE-2026-109618<\/p>\n\n

Out-of-memory handling can leave internal PHP request data in an invalid state.<\/p>\n <\/div>\n\n

\n

CVE-2026-109619<\/p>\n\n

Internal request state may be reused after its memory has been freed.<\/p>\n <\/div>\n\n <\/div>\n\n

\n

Patched PHP versions<\/p>\n\n

8.2.35  \u00b7  8.3.36  \u00b7  8.4.27  \u00b7  8.5.12<\/p>\n <\/div>\n\n

Older PHP branches require an appropriate security backport from your vendor or an upgrade to a supported version.<\/p>\n\n

More details: Official PHP security advisory →<\/a><\/p>\n\n<\/div>\n\n\n\n

Security updates are ready, here is what to do<\/h2>\n\n

We have released the following versions with the PHP security fixes. Please update the products you use, and check the notes below before you begin.<\/p>\n

\n

PanelAlpha Control Panel \u2192 update to v1.9.8.3<\/h3>\n

Back up your server and database, review the changelog, and make sure you have root SSH access and your license key. Then connect to the PanelAlpha server and run the update command below. The installer detects your existing installation and updates it.<\/p>\n

UPDATE COMMAND<\/p>\n

curl -fsSL https:\/\/get.panelalpha.com\/app | sh<\/code><\/pre>\n
For system requirements and troubleshooting, follow the PanelAlpha update guide<\/a>.<\/p>\n<\/div>\n
\n
PanelAlpha Engine 1.x \u2192 update to v1.0.23.1<\/h3>\n
Back up your server and data and check the changelog before proceeding. Connect as root, download the updater and run it with your PanelAlpha license key. Services may restart briefly, so plan for possible downtime. Afterwards, check the server status in PanelAlpha and create a test instance.<\/p>\n
UPDATE COMMAND<\/p>\n
wget -N -P \/opt\/panelalpha https:\/\/license.panelalpha.com\/engine-updater.sh\nbash \/opt\/panelalpha\/engine-updater.sh --key 'YOUR_LICENSE_KEY'<\/code><\/pre>\n
See the Engine 1.x update guide<\/a> for the complete procedure and recovery instructions.<\/p>\n<\/div>\n
\n
PanelAlpha Engine 2.x \u2192 update to v2.1.2.1<\/h3>\n
On your Engine VPS, sign in as root and note your current version with pae system:version<\/code>. Run the update command below, then check the version again and open one of your websites to confirm it works. The Engine restarts during the update, but existing hosted websites are not rebuilt.<\/p>\n
UPDATE COMMAND<\/p>\n
curl --proto '=https' -fsSL https:\/\/get.panelalpha.com\/engine | sh<\/code><\/pre>\n
Full details are in the Engine 2.x update guide<\/a>.<\/p>\n<\/div>\n
\n
Important before updating<\/p>\n
Using Control Panel with Engine.<\/strong> If you’re running both, please stick with Engine 1.x for now and update it to v1.0.23.1. We’re already working on a dedicated Control Panel update that will make it compatible with Engine 2.x.<\/p>\n
WordPress sites need their own PHP updates.<\/strong> Updating PanelAlpha Engine will not automatically update the PHP version used by your existing WordPress sites. Sites still running an unpatched PHP build will remain at risk. Check and update the PHP version for each WordPress installation separately.<\/p>\n<\/div>\n\n
Where else to check PHP in your setup<\/h2>\n\n
Updating PanelAlpha and Engine takes care of their respective components, but it does not patch every PHP installation on your servers. These are the other places worth checking.<\/p>\n
\n
WHMCS and the PanelAlpha module for WHMCS<\/h3>\n
WHMCS usually runs on a different server from PanelAlpha and uses that server\u2019s PHP installation. You or your hosting provider will need to patch that PHP separately. PanelAlpha WordPress Hosting For WHMCS<\/strong><\/a> module supports PHP 8.2 and 8.3, but please check that your WHMCS version, ionCube Loader and other dependencies support the patched build before switching.<\/p>\n<\/div>\n
\n
PHP sites hosted on PanelAlpha Engine<\/h3>\n
Each PHP project has its own PHP environment, which may need a separate update or rebuild depending on how the project is deployed. Check traditional and container-based projects, and do not forget cron jobs: they may use a different PHP version from the website. Updating the panel or Engine itself does not automatically patch PHP inside every existing project.<\/strong><\/p>\n<\/div>\n\n
Security cheat sheet for admins<\/h2>\n\n
    \n
  1. Make a list of everywhere PHP is running, including WHMCS, customer sites and less obvious services such as billing cron jobs or a status page.<\/li>\n
  2. Check the PHP version used by each website and by its cron jobs. They are not always the same.<\/li>\n
  3. Make sure each PHP environment receives an officially patched build. The patch level matters more than the version number alone.<\/li>\n
  4. Check compatibility with WHMCS, ionCube Loader, PHP extensions and any integrations you depend on.<\/li>\n
  5. Back up your files, configuration and databases. Test in staging first if you can. PanelAlpha Engine lets you create a staging copy of a project, including its databases.<\/li>\n
  6. If your hosting provider manages PHP for you, ask them to confirm when the security update has been applied.<\/li>\n
  7. Apply the available updates promptly, then verify the versions and test the services you rely on.<\/li>\n<\/ol>\n\n
    Check that everything still works<\/h2>\n\n
    Once you have updated, test every single flow your team and customers rely on every day: admin and client logins, checkout, invoices, payments, cron jobs and API integrations. If you use the WHMCS module, also check account creation, suspension, unsuspension, termination and single sign-on to the panel. Finally, look through the error logs. A page loading normally is a good start, but it does not tell you that everything behind it is working.<\/p>\n\n
    A few more security checks worth making<\/h2>\n\n
    These checks do not replace the PHP fixes, but they are still worth doing while you are reviewing your setup.<\/p>\n