phpAfterShell (CVE-2026-126714): PHP Session Flaw Explained
phpAfterShell, CVE-2026-126714, lets attackers plant objects in PHP session files. Affected and fixed PHP versions, how to protect your server, and what HostGrap did.
A cPanel & WHM flaw let resellers with the ssl permission run code as root. Patched versions, how to update or remove the permission, and what HostGrap did.
On 19 November 2026, cPanel released a security update for a vulnerability in how cPanel & WHM processes SSL certificates for resellers. A reseller who has the ssl permission in WHM could use it to run code as root, which means full control of the server. Every supported version of cPanel & WHM and WP Squared is affected, and the fix is to update to a patched version. All HostGrap hosting servers have been updated, so shared hosting and reseller customers don't need to do anything. If you run cPanel & WHM on your own HostGrap VPS or VDS, you need to update it yourself.
cPanel & WHM lets a server administrator create reseller accounts, and each reseller can be given permissions, also called privileges, in WHM. One of them is the ssl permission, which lets a reseller install and manage SSL certificates for the cPanel accounts they own.
cPanel found that the way SSL certificates from resellers were processed could be abused. A reseller with the ssl permission could make the server run their own code as root, the most powerful user on a Linux server. Root can read, change or delete anything on the server, including every other customer's website, email and database. That is why cPanel treats this as a serious issue, even though only resellers with that permission can use it.
The issue affects servers that run cPanel & WHM or WP Squared and have at least one reseller account with the ssl permission. If you rent hosting, a reseller plan or a cPanel account from a hosting company, the hosting company has to update its servers, and there is nothing to change in your own account. If you run your own server with cPanel & WHM, such as a VPS or a dedicated server, you are the server administrator, so you need to update it yourself.
A server with no reseller accounts, or with resellers who don't have the ssl permission, can't be attacked through this issue. It should still be updated, because the update also protects you if you add resellers later.
cPanel fixed the issue in the versions below. Your server is protected when it runs one of these versions or any later version on the same release.
| Product | Patched versions |
|---|---|
| cPanel & WHM | 11.138.0.28, 11.136.0.54, 11.134.0.77, 11.110.0.164 |
| WP Squared (WP2) | 11.136.0.54, 11.138.1.22 |
We updated cPanel & WHM on all of our hosting servers, the ones that run our cPanel, WordPress, business and reseller hosting, to a patched version.
Because the servers are patched, we did not need to take the ssl permission away from our resellers. HostGrap reseller customers can keep installing and managing SSL certificates for their clients as before, and every domain still gets its free SSL certificate automatically. There is nothing you need to do in your WHM or cPanel.
If you run your own cPanel server, log in to WHM and look at the version number at the top of the page, or connect to the server over SSH as root and run this command:
/usr/local/cpanel/cpanel -VCompare the number with the table above. If your version is lower than the patched version for your release, update the server.
In WHM, open Upgrade to Latest Version, which is under cPanel in the menu, and click Click to Upgrade. You can also update over SSH as root with this command:
/scripts/upcpThe update can take several minutes, and websites usually keep working while it runs. When it has finished, check the version again to make sure the server is on a patched version. To keep your server safe from future issues, open Update Preferences in WHM and make sure cPanel & WHM updates are set to install automatically. cPanel's guide on how to update cPanel & WHM explains each option.
cPanel's advice is to remove the ssl permission from your resellers until you can update. You can do this for one reseller at a time in WHM, under Edit Reseller Nameservers and Privileges, by clearing the ssl permission and saving. cPanel's guide on editing reseller privileges shows where to find it.
To remove it from every reseller at once, cPanel gives this command, to run over SSH as root. It saves a backup copy of the resellers file with today's date before it makes the change:
sed -i.bak.$(date +%F) 's/,ssl,/,/g' /var/cpanel/resellersWhile the permission is removed, your resellers can't install or manage SSL certificates for the accounts they own, so tell them before you do it. After you have updated to a patched version, you can give the ssl permission back in Edit Reseller Nameservers and Privileges.
It depends on your service. If you have cPanel, WordPress, business or reseller hosting, you don't need to do anything: our servers are on a patched version of cPanel & WHM, and your hosting, reseller accounts and SSL certificates work as before.
If you have a HostGrap VPS or VDS with cPanel & WHM installed, you are the server administrator, so you need to update it yourself. Follow the steps above to check your version and update, and if you can't update straight away, remove the ssl permission from any resellers on your server until you can. A VPS or VDS without cPanel & WHM is not affected by this issue. If you have a question about this update, or about the security of your website, message us on WhatsApp or open a support ticket, and HostGrap AI or our team will help. To learn more about how we protect our servers, read our WordPress security checklist and our reseller hosting guide.
phpAfterShell, CVE-2026-126714, lets attackers plant objects in PHP session files. Affected and fixed PHP versions, how to protect your server, and what HostGrap did.
A plain-words WordPress security checklist: updates, unused plugins, strong logins, SSL, backups, hosting security and what to do if your site is hacked.
CVE-2026-119977 lets attackers run code while WordPress updates. HostGrap already blocks wp-content/upgrade on every server. Here is how to update to 7.1.4 safely anywhere else.