Screenshots of the Australian Cyber Security Centre critical alert on PHP vulnerabilities and the Dapth Xperience by Kentico page, on desktop and mobile

Digital Consultancy · Website security

Know where PHP runs, and whether it can be patched

Two critical flaws in PHP were flagged by the Australian Cyber Security Centre (ACSC) on 21 October 2026. Fixes are out for PHP 8.2 to 8.5, and some older versions have no official fix. This week, list every website and app you run, find the PHP, check the version, then patch or isolate what you cannot patch. The bigger point is that you can only patch what is still supported, and the update model behind your platform decides how fast fixes reach you. This article gives you the version table, a short checklist, and what it means for Xperience by Kentico and the 31 December 2026 support end for Kentico Xperience 13.

Key takeaways

  • The ACSC rated the alert critical and says all PHP versions from PHP 5 onwards may be affected.
  • Fixed releases are PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP 7.4, 8.0 and 8.1 have no official release, and PHP 7.3 and older have no fix.
  • This week: list every site and app, find the PHP, check the version, then patch or isolate what you cannot patch.
  • You can only patch what is still supported, so support dates decide how fast you can respond.
  • Kentico says its evergreen model ships hotfixes weekly. Support for Kentico Xperience 13 ends on 31 December 2026.

What happened with PHP this week?

On Wednesday 21 October 2026, the ACSC, which is part of the Australian Signals Directorate, published a critical alert on two vulnerabilities in PHP, CVE-2026-109618 and CVE-2026-109619. Both are rated 9.2 out of 10. They can allow unauthenticated remote code execution, which means an attacker could run code on a web server without logging in. The first involves memory corruption when a request runs out of memory. The second involves stale state that a later request on the same worker can abuse. The ACSC says all PHP versions from PHP 5 onwards may be affected.

Researchers at Calif, working with OpenAI and Wiz, found the flaws with help from AI, and the planned disclosure leaked early. By Thursday morning several Australian government websites had been taken offline temporarily while the risk was reduced. Reports differ on exploitation. The ACSC says it is not aware of successful active exploitation within Australia, while security firm watchTowr says it has seen exploitation since 21 October.

Which PHP versions are fixed, and which have no fix?

The PHP project fixed both flaws in its four supported branches. Anything older needs a vendor or long-term-support package, a backport or an upgrade. PHP says no configuration change fully mitigates the flaws, so updating and restarting every PHP worker is the fix.

PHP versionOfficial fixWhat to do
PHP 8.5Fixed in 8.5.12Update to 8.5.12 or later and restart all PHP workers.
PHP 8.4Fixed in 8.4.27Update to 8.4.27 or later and restart all PHP workers.
PHP 8.3Fixed in 8.3.36Update to 8.3.36 or later and restart all PHP workers.
PHP 8.2Fixed in 8.2.35Update to 8.2.35 or later and restart all PHP workers.
PHP 8.1, 8.0 and 7.4No official releaseUse a vendor or long-term-support package or a backport, or upgrade to a supported branch.
PHP 7.3 and older, including PHP 5No fixUpgrade to a supported branch, and restrict internet access to the system until you do.

As at 23 October 2026, from watchTowr's FAQ. Check php.net for the latest releases before you act.

What should you check this week?

The ACSC's advice is to identify PHP in your environment, review PHP's guidance, apply updates and monitor for suspicious activity. In practice that becomes six steps you can finish this week.

  1. List every website, app and server you run, including old microsites, staging sites and anything run by an agency or vendor.
  2. Find the PHP. WordPress, Drupal, Joomla and Magento all run on PHP, as do many custom builds. If you are unsure, ask your host or agency.
  3. Check the version. Ask your host, or run php -v on the server. The command-line version can differ from the one serving your website, so confirm which one handles web requests.
  4. Compare it with the table above.
  5. Back up first, then patch and restart all PHP workers. If your version has no official fix, move to a supported branch or use a vendor package.
  6. Name an owner and a deadline for each system, and monitor for suspicious activity.

If you cannot patch something today, restrict internet access to it until you can. watchTowr advises this for anything you cannot patch straight away, and the ACSC's guidance points the same way.

Why do support dates decide how fast you can fix things?

Patching only works on software that is still supported. End of support means the vendor stops releasing updates, including security fixes, while the software keeps running. That is why the table above has rows that say no fix. A flaw in a supported version gets a patch. The same flaw in an unsupported version stays open.

The same logic applies to your platform. Kentico's support lifecycle page lists 31 December 2026 as the end of technical support for Kentico Xperience 13. Until then, Kentico says releases are limited to security hotfixes. From 1 January 2027, it says all support, updates and security repairs stop. Your site will not switch off, but it will stop receiving fixes. If your site is on Kentico Xperience 13, plan the move to Xperience by Kentico now, while you can still choose the pace.

What does an evergreen platform change?

An evergreen platform ships changes continuously instead of in large versions. Kentico says Xperience by Kentico ships hotfixes weekly and feature refreshes monthly, with a 7-day security bug-fix policy for the latest release. On its SaaS option Kentico handles infrastructure and versioning. On private cloud your team decides when to apply updates, with partner support. Kentico's marketing says you never need to upgrade again, but its own FAQ is more careful: updating means reading the release notes and applying updates when needed.

In our view, the real benefit is that staying current becomes routine, not a project. That is what lets a team respond within days when an alert lands.

Is Kentico affected by these PHP flaws?

No. Both flaws are in the PHP runtime, and Xperience by Kentico runs on .NET, so they are not in its stack. The same goes for Kentico Xperience 13, which is also a .NET product. The checklist above still applies, because PHP can run next to your Kentico site: an old microsite, a blog or a vendor-run tool. If you are not sure what runs where, that is the first thing to find out.

A patch is only as fast as the support behind it. If you want help working out where PHP runs, or planning the move off Kentico Xperience 13, our Xperience by Kentico team can start with what your site does for you today.

About Dapth

Dapth is your Perth digital consultancy, building connected digital systems from websites and intranets to applications, software, ERP and AI tools. For more than 15 years we have helped WA businesses, government agencies and organisations unlock advantages like streamlined workflows, increased efficiency, cost savings, new revenue and more powerful marketing.

We start with your organisation, not the technology: your users, your operations and your objectives. Then we connect everything across four areas:

Not sure where PHP runs in your business, or what the Xperience 13 support end means for you? Talk to us and we will start with what your site does for you today.

Talk to Dapth

Frequently asked questions

What are CVE-2026-109618 and CVE-2026-109619?

They are two critical flaws in PHP, rated 9.2 out of 10, that can allow unauthenticated remote code execution on a web server. CVE-2026-109618 involves memory corruption when a request runs out of memory. CVE-2026-109619 involves stale state that a later request can abuse. The ACSC issued a critical alert on 21 October 2026 and says all PHP versions from PHP 5 onwards may be affected.

How do I check my PHP version?

Ask your host or agency, or run php -v on the server. The command-line version can differ from the one that serves your website, so confirm which version handles web requests. Then compare it with the version table above. If you cannot tell, treat the system as unchecked and ask the people who run it.

What are the risks of running an unsupported PHP version?

Unsupported versions stop receiving security fixes, so any newly found flaw stays open. That is the position of PHP 7.3 and older in this alert, which have no fix at all. If you cannot upgrade straight away, restrict internet access to the system until you can.

What if my PHP version has no official fix?

For PHP 7.4, 8.0 and 8.1, watchTowr says there is no official release, so use a vendor or long-term-support package, a backport, or upgrade. For PHP 7.3 and older, including PHP 5, there is no fix, so upgrade to a supported branch. Restrict internet access to the system in the meantime.

Do SaaS platforms apply security updates for you?

It depends on the model. Kentico says that on Xperience by Kentico SaaS it handles infrastructure and versioning, and that it ships hotfixes weekly with a 7-day security bug-fix policy for the latest release. On private cloud, your team decides when to apply updates. Either way, custom code and add-ons still need an owner.

What does end of support mean for Kentico Xperience 13?

Kentico lists 31 December 2026 as the end of technical support for Kentico Xperience 13. Until then, releases are limited to security hotfixes. From 1 January 2027, Kentico says all support, updates and security repairs stop. The site keeps running, but it stops receiving fixes. Plan the move to a supported platform such as Xperience by Kentico now.

Sources

  1. ASD's Australian Cyber Security Centre, Critical vulnerabilities in PHP, published 21 October 2026, reviewed 22 October 2026.
  2. iTnews, Critical flaws strike PHP as disclosure embargo is broken, 21 October 2026.
  3. Information Age, Govt sites go down after AI finds critical PHP vulnerabilities, October 2026.
  4. watchTowr, PHP2Shell FAQ: CVE-2026-109618 and CVE-2026-109619 fixes
  5. Kentico, Evergreen platform
  6. Kentico, Support lifecycle

Related insights

Author
Founder & Chief Strategist
Get in touch

We transform

Discover More insights.

One thing we won't apologise for? Our passion for the digital world.