Security · PHP flaw
A critical PHP flaw took websites offline. Scalus sites were never affected
On Wednesday 21 October 2026 the people who look after PHP released an urgent security fix. PHP is the language underneath most WordPress sites, and Drupal and Joomla sites too. The flaw, known as PHP2Shell (CVE-2026-109618 and CVE-2026-109619), lets an attacker take over a site without logging in, and attacks had already started.
What happened
It is rated critical, and it reaches every version of PHP from 5.4 onwards, which covers more than ten years of websites. Within a day, councils, universities and governments around the world took their websites offline while they patched.
What I did
I checked every Scalus website on the morning of 22 October, one by one. Not one of them runs on PHP, so none of them was exposed and none had to come down.
Every Scalus site checked the next morning. Not one runs on PHP.
Why Scalus sites were never affected
Scalus sites are not built on WordPress and a pile of plugins. The platform is updated every day, there are no plugins to fall behind, and there is no server sitting somewhere waiting for a business owner to log in and patch it. Every client's data and systems sit behind the same safeguards, whether they joined last year or last week.
I now also check worldwide security alerts four times a day, so the next one is looked at the morning it lands.
If your website runs on WordPress
Ask your host one question this week: has PHP had the 21 October security update? These versions have the fix:
- PHP 8.5: 8.5.12 or later
- PHP 8.4: 8.4.27 or later
- PHP 8.3: 8.3.36 or later
- PHP 8.2: 8.2.35 or later
PHP 7.4, 8.0 and 8.1 get no official fix. If your site is on one of those, ask your host to move it to 8.2.35 or later. If they are not sure, ask them to check today.