Current status
| Server | Status |
|---|---|
| Firewall protection (all servers) | ✓ In place |
| Enhance servers – all PHP versions | ✓ Fixes installed |
| cPanel servers – all PHP versions | ✓ Fixes installed |
| New: CVE-2026-115560 (session upload progress) | ✓ Already protected – by the setting we switched off on 21/10/26 |
What is the issue?
The PHP project announced two critical security issues, which have become known as PHP2Shell. On a server without protection, they could let an attacker run their own code on a website simply by sending it specially crafted requests – without needing a login.
| Detail | Information |
|---|---|
| Affected software | PHP |
| Known as | PHP2Shell – CVE-2026-109618 and CVE-2026-109619 |
| Type | Remote code execution, without a login |
| Severity | Critical (rated 9.2 out of 10) |
| Fixed in | PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, released 21 October 2026 |
What we have done
- 21/10/26, before the fix: added firewall rules that block the known attack attempts – cPFence on our Enhance servers and Imunify360 on our cPanel servers – and switched off a little-used PHP feature that’s being targeted (
session.upload_progress.enabled). - 21/10/26: installed the fixed versions of PHP 8.2, 8.3, 8.4 and 8.5 on our Enhance servers, and restarted PHP.
- 22/10/26: installed the fixes for every PHP version on our cPanel servers, and for PHP 7.4, 8.0 and 8.1 on our Enhance servers.
- 23/10/26: PHP announced a further issue, CVE-2026-115560. Our servers were already protected against it by the session upload progress setting we switched off on 21/10/26, so no further action was needed.
- 24/10/26: installed the fixes for all remaining PHP versions on our Enhance servers. Every PHP version on all our servers now includes the fix.
- Next: installing PHP’s next regular release, which includes the full fix for CVE-2026-115560, as soon as it’s available. Our servers are already protected against it in the meantime.
What about CVE-2026-115560?
On 23 October 2026, PHP announced a further, related issue: CVE-2026-115560. It has been widely reported, but it only affects websites with an unusual combination of settings and code, and PHP describes it as an unlikely route for an attack.
PHP will include a full fix in its next regular release, and we’ll install it as soon as it’s available. Until then, the setting stays switched off.
Do I need to do anything?
No. If your website or email is hosted with us, we’re taking care of this for you.
Why hasn’t my PHP version number changed?
PHP fixed these issues by releasing new version numbers: 8.5.12, 8.4.27, 8.3.36 and 8.2.35. On our servers, the same fix has also been added directly to the PHP versions already installed. This is called a backport, and it’s how fixes reach older PHP versions that PHP itself no longer updates.
So your website might show a version that looks older than the fixed releases, for example:
| Your website shows | Does it include the fix? |
|---|---|
| PHP 8.4.26 | ✓ Yes, on our servers – the fix has been added to this version |
| PHP 8.5.11 | ✓ Yes, on our servers – the fix has been added to this version |
| PHP 7.4, 8.0 or 8.1 | ✓ Yes, on our servers – these versions only receive fixes this way |
The version numbers will catch up in a later routine update. You don’t need to do anything when that happens.
Running your own server?
If you have a VPS or dedicated server that you manage yourself using the Enhance control panel, install the fixed PHP versions if you haven’t already. Connect over SSH and run:
apt update
apt upgrade -y
ecp restart-php This installs the fixed builds of every PHP version and restarts PHP. Keep session.upload_progress.enabled set to Off until PHP’s next regular release, as it also protects against CVE-2026-115560.
Using cPanel on your own server? Install the latest ea-php (and CloudLinux alt-php, if you use it) packages. To check a PHP version includes the fix, look for the CVE numbers in its package changelog, for example:
rpm -q --changelog ea-php84-php-cli | grep -E 'CVE-2026-(109618|109619)'
rpm -q --changelog alt-php85-common | grep -E 'CVE-2026-(109618|109619)' If the CVE numbers are listed, that version is fixed, even if its version number hasn’t changed.
Was my website affected?
We are not aware of any websites on our platform being compromised as a result of these issues. Our firewall rules and extra hardening were in place before the fix was released, and stayed in place until it was installed on every server. If you have any concerns about your website, we’re always happy to take a look – and if you think something isn’t right, see what to do if your website has been hacked.