A Vaksincom scan of servers in Indonesia as of 23 October 2026 read 99,896 PHP versions. Of those, 69,546, or 69.6%, were already end-of-life. Only 226 readings, about 0.2%, were recorded as running the latest patched release. Katadata reported the figures on 26 October 2026.

If your website was built by an agency, those numbers lead to one plain question: which PHP version is your site running on? If nobody can answer, that is already a finding.

Three numbers from the Vaksincom scan: 99,896 PHP versions read, 69.6% already end-of-life, 0.2% running the latest patch

Not a late update, a patch that does not exist

This difference is easy to miss. A site that is late on updates can be rescued with one version upgrade, because the patch exists. A site on end-of-life PHP is different: the maintainers have stopped releasing security fixes, so a flaw found today will never be closed on that version.

The version found most often in the scan was PHP 5.6.40. Its official security support ended at the end of 2018, almost eight years ago.

The front page gives no sign of any of this. The layout looks normal, the contact form sends, transactions go through. A website can look perfectly fine on top of a machine its makers abandoned, and an owner has no way to tell from the screen.

Which sectors

Among government domains (.go.id), Vaksincom detected 2,072 hosts and read 1,677 PHP versions. Of these, 1,621, or 96.7%, were on end-of-life PHP. Company domains (.co.id) showed the same share: 4,495 of 4,650 readable versions. Universities (.ac.id) stood at 88.7%, which is 439 of 495, and schools (.sch.id) at 69.9%, which is 51 of 73.

Vaksincom did not publish domain or agency names. The findings were shared privately with BSSN or the infrastructure owners.

Bar chart of the share of end-of-life PHP versions by domain type: .go.id 96.7%, .co.id 96.7%, .ac.id 88.7%, .sch.id 69.9%, all readings 69.6%

Why it is urgent: PHP2Shell

Katadata describes PHP2Shell as a critical vulnerability that lets attackers take over PHP servers through remote code execution, without logging in. The fixed releases it names as safe are PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12.

Note the list: four branches only. A server on an older branch has no fixed release to install, so the only way out is to upgrade. Komdigi issued three advisory letters on 9 November 2026, after a BSSN Security Advisory on 8 November. Among other things they ask institutions to update software and make sure data is backed up.

Read the numbers carefully

Three notes keep the figures from being over-read. First, only servers that expose their PHP version can be counted. Second, servers behind a CDN such as Cloudflare are not captured. Third, Katadata notes that the number of servers detected as patched does not necessarily reflect everything that is protected, because Linux distributions can backport fixes without changing the version number.

So the 0.2% figure probably undercounts. But the 69.6% that is end-of-life is still large, and the direction is the same in every sector.

When each branch stops getting patches

According to the supported versions page on php.net, as of 21 November 2026 security support for PHP 8.5 runs until 31 December 2029, PHP 8.4 until 31 December 2028, PHP 8.3 until 31 December 2027 and PHP 8.2 until 31 December 2026. Branch 8.1 and older are no longer in the supported-versions table.

Timeline of PHP security support ending: 5.6 end of 2018, 8.2 on 31 December 2026, 8.3 on 31 December 2027, 8.4 on 31 December 2028

In other words, a site running PHP 8.2 today is already counting down. It needs to be upgraded before 31 December 2026, after testing in a staging environment.

Three questions for your agency

Put these to the agency or vendor that runs your website:

  1. Which PHP version is in use right now? Ask for the full number, for example 8.4.27. "The latest" is not enough.
  2. Until when does that version receive security patches? Check the answer against the table on php.net.
  3. When will it be upgraded? Ask for a date, not "we will check".
Four steps from the question to the agency to the contract clause: ask the version, check php.net, ask for an upgrade date, put it in the contract

Our view: put it in the maintenance contract

A verbal answer leaves with the person who gave it. That is why we think these three items belong in the maintenance contract: the current PHP version, the date security patches end for it, and the latest date for the upgrade. Then, when a version nears its limit, someone is clearly responsible for upgrading it, instead of waiting for the site to run into trouble.

One note on shared hosting: the PHP version is often set by the hosting provider, not the agency. Ask the provider too, and have the version and upgrade schedule recorded.

Today, send your agency one email with the three questions above and ask for a written reply before 31 December 2026. If you would like the PHP version of your website checked, contact us at bisnis@xetup.id or WhatsApp +62 823 1499 5005.

Sources