Skip to content
Sri Lanka Update Current English

PHP Security Vulnerabilities: Are Sri Lankan Government and Company Websites at Risk?

Peak Lanka editorial Published Last updated

Two critical security vulnerabilities in PHP have triggered urgent security updates for websites and servers around the world.

The vulnerabilities, disclosed on October 21, 2026, can potentially allow an attacker to execute malicious code on a vulnerable web server without first logging in.

The official PHP Security Team has urged PHP users to update immediately. You can read the official PHP security advisory.

For Sri Lanka, this matters because PHP is widely used behind websites built with platforms such as WordPress, Drupal, Joomla and custom web applications. That potentially includes websites operated by businesses, universities, government organisations, media companies and other public-facing services.

However, an important distinction needs to be made: a website running PHP is not automatically hacked, and at the time of publishing there is no confirmed evidence reviewed by Peak Lanka showing that a Sri Lankan government website or major Sri Lankan company has been compromised specifically through these newly disclosed PHP vulnerabilities.

The risk is nevertheless serious enough that website owners, hosting providers and IT teams should check their PHP environments immediately.

What Happened?

On October 21, 2026, the PHP project released security updates addressing two critical vulnerabilities:

  • CVE-2026-109618 — remote code execution related to out-of-memory corruption.
  • CVE-2026-109619 — remote code execution related to stale global state.

Both vulnerabilities have been given a CVSS v4.0 score of 9.2 out of 10, placing them in the critical severity category.

The vulnerabilities are also being referred to as PHP2Shell.

Unlike a vulnerability affecting one specific WordPress plugin, theme or CMS, these vulnerabilities exist in PHP itself. PHP is the server-side programming language used underneath millions of websites and web applications.

Security authorities in Europe have also issued warnings. ENISA, CERT-EU, Europol EC3 and other cybersecurity organisations advised organisations to identify PHP-based applications and urgently patch internet-facing systems.

You can read the ENISA joint statement on the critical PHP vulnerabilities.

Which PHP Versions Should Be Updated?

The PHP project released the following patched versions on October 21:

PHP Branch Previous Release Patched Version
PHP 8.5 8.5.11 8.5.12
PHP 8.4 8.4.26 8.4.27
PHP 8.3 8.3.35 8.3.36
PHP 8.2 8.2.34 8.2.35

Website administrators should therefore check the actual PHP runtime installed on their server, rather than simply checking whether WordPress, plugins or themes are updated.

For example, a website running PHP 8.3.35 should be updated to PHP 8.3.36 or a later security-fixed version.

The latest official PHP releases can be checked on the PHP downloads page.

What About PHP 8.1, PHP 8.0 and PHP 7.x?

PHP 8.1 and older versions no longer receive normal security releases from the PHP project.

Because of the severity of these vulnerabilities, the PHP team has provided minimal source backports for PHP 7.4, PHP 8.0 and PHP 8.1 to help organisations that build PHP themselves or cannot immediately access a long-term-support vendor update.

Some Linux distributions, hosting companies and long-term-support vendors may also provide backported security fixes.

This means an older displayed PHP version number does not always prove that a particular managed server remains vulnerable. Administrators using an older PHP branch should confirm the patch status directly with their operating-system or hosting provider.

However, continuing to rely on an unsupported PHP version creates unnecessary long-term security and maintenance risk.

Why Are These PHP Vulnerabilities So Serious?

The biggest concern is remote code execution, commonly called RCE.

In simple terms, remote code execution can potentially allow an attacker to cause a vulnerable server to execute code chosen by the attacker.

The PHP Security Team says installations serving web requests may be affected, including environments using:

  • PHP-FPM;
  • Apache with mod_php;
  • php-cgi;
  • FrankenPHP; and
  • LiteSpeed.

PHP has said the demonstrated risk is particularly serious for Apache mod_php, where an unauthenticated request may potentially trigger exploitation before the website application’s own code begins running.

Depending on the server configuration and successful exploitation, an attack could potentially result in:

  • website takeover;
  • malicious files or backdoors being installed;
  • website content being modified;
  • sensitive server information being exposed;
  • credentials or secrets being accessed;
  • websites being used for further attacks; or
  • services becoming unavailable.

Are WordPress Websites Affected?

WordPress itself is not the cause of these PHP vulnerabilities.

However, WordPress runs on PHP. A WordPress website hosted on an affected PHP environment may therefore be exposed through the underlying PHP runtime.

Security researchers at Wiz demonstrated the vulnerabilities against common PHP applications, including WordPress, Drupal and Joomla. Their research emphasises that the underlying issue exists in PHP rather than those CMS platforms themselves.

You can read the Wiz PHP2Shell technical analysis for more technical information.

This creates an important difference from a normal WordPress vulnerability.

Updating:

  • WordPress core;
  • plugins; and
  • themes

is still important, but those updates alone do not fix a vulnerability in the PHP runtime.

The PHP environment on the server must also receive the appropriate security fix.

Are Sri Lankan Government Websites at Risk?

Potentially — if they are operating internet-facing applications on affected PHP environments.

Sri Lankan government websites and online services use a variety of technologies, hosting providers and software platforms.

It would therefore be incorrect to claim that all Sri Lankan government websites are vulnerable simply because PHP vulnerabilities exist.

The relevant question for each organisation is:

Does the organisation operate an internet-facing application using an affected PHP environment that has not received the security fix?

If the answer is yes, it should be treated as a high-priority security issue.

It is also important to understand that the exact PHP version used by a website cannot always be reliably determined from outside. Properly configured web servers often deliberately hide information about their underlying software versions.

For that reason, Peak Lanka is not labelling individual Sri Lankan government websites as vulnerable without reliable evidence.

What About Sri Lankan Banks and Companies?

The same rule applies to banks, telecommunications companies, retailers, universities, media organisations and other Sri Lankan businesses.

Some organisations may not use PHP at all.

Others may use PHP only for:

  • their main corporate website;
  • customer portals;
  • internal applications;
  • WordPress marketing websites;
  • APIs; or
  • older business systems.

Some may also have already received the security fix automatically from their hosting or infrastructure provider.

Therefore, simply discovering that a company’s website uses WordPress or PHP is not sufficient evidence to claim that the organisation is vulnerable.

Can Cloudflare Protect Websites From PHP2Shell?

Cloudflare has deployed Web Application Firewall protections against PHP2Shell.

According to Cloudflare, protections were deployed ahead of the public disclosure, and customers using its WAF were protected against the known PHP2Shell attack techniques.

Cloudflare also reported observing attackers attempting to modify exploit payloads to bypass protections after information about the vulnerabilities became public.

You can read Cloudflare’s PHP vulnerability and WAF protection guidance.

This is useful protection, particularly while hosting companies are rolling out PHP updates.

However, Cloudflare is not a replacement for updating PHP.

A WAF can block known attack patterns and reduce exposure, but PHP itself remains vulnerable until the underlying environment receives the security fix.

The safest approach is therefore:

Update PHP first, while keeping Cloudflare or another WAF enabled as an additional security layer.

What Should Sri Lankan Website Owners Do Now?

If you manage a business website, WordPress website, e-commerce platform, government system or another PHP application, there are several practical steps to take.

1. Check Your PHP Version

Your PHP version may be visible through:

  • your hosting control panel;
  • cPanel;
  • Cloudways or another hosting dashboard;
  • WordPress Site Health;
  • your server administration tools; or
  • your hosting provider’s support team.

2. Install the Patched PHP Version

For the currently supported PHP branches, the October 21 security releases are:

  • PHP 8.5.12
  • PHP 8.4.27
  • PHP 8.3.36
  • PHP 8.2.35

PHP’s official guidance is clear that updating is the complete solution to the underlying vulnerabilities.

See the official PHP security release notice.

3. Contact Your Hosting Provider If You Cannot Update

If the latest PHP version is not available in your hosting dashboard, contact your hosting provider.

Ask whether:

  • the security patch has already been installed;
  • they are using a vendor-provided backported fix;
  • a PHP security update is being deployed automatically; and
  • you need to perform any action from your side.

4. Keep Your WAF Enabled

If you use Cloudflare or another Web Application Firewall, keep it enabled.

It provides another security layer, but do not use it as an excuse to delay the underlying PHP update.

5. Review Logs for Suspicious Activity

Administrators should also review server, application and security logs for unusual behaviour.

Depending on the infrastructure, warning signs could include:

  • unexpected PHP processes;
  • unusual HTTP requests;
  • unexpected files appearing on the server;
  • new administrator accounts;
  • unexplained configuration changes;
  • outbound connections from the web server; or
  • other indicators of compromise.

6. Restart Services When Required

Some security fixes or mitigation changes require PHP workers and related services to be restarted.

Administrators should follow the instructions from their Linux distribution, hosting company or infrastructure provider rather than assuming an update has taken effect immediately.

7. Plan to Move Away From Unsupported PHP Versions

If a production website still depends on PHP 7.x, PHP 8.0 or PHP 8.1, this incident is another reason to plan an upgrade.

Legacy applications can make PHP upgrades difficult, but remaining indefinitely on unsupported software creates an accumulating security risk.

What If Your Hosting Dashboard Still Shows PHP 8.3.35?

This may happen while managed hosting providers roll out newly released PHP packages.

For example, if your hosting dashboard still lists PHP 8.3.35 as the latest selectable PHP 8.3 release, the official upstream security release is now PHP 8.3.36.

That does not automatically prove your hosting provider has failed to patch the server.

Linux distributions and hosting providers can sometimes apply security patches to their own packages while retaining a versioning scheme different from PHP’s standard upstream release.

The correct approach is to contact the hosting provider and ask them to confirm whether CVE-2026-109618 and CVE-2026-109619 have been patched.

Should Ordinary Sri Lankan Internet Users Be Worried?

Ordinary website visitors do not currently need to stop using every website built with PHP.

The immediate responsibility lies mainly with:

  • website owners;
  • developers;
  • hosting providers;
  • system administrators;
  • IT departments; and
  • cybersecurity teams.

If a particular bank, government service, company or online platform later confirms that its systems were compromised or that customer information was exposed, users should then follow the security guidance relating to that specific incident.

That could include changing passwords, monitoring financial accounts or taking other precautions depending on the type of information involved.

Does a Vulnerable PHP Version Mean the Website Has Been Hacked?

No.

This is one of the most important distinctions to understand.

A vulnerability means a weakness exists that an attacker may potentially exploit.

A compromise means an attacker has actually succeeded in gaining unauthorised access or affecting the system.

Those are not the same thing.

This distinction is especially important when discussing banks, companies and government institutions.

Claims that a particular organisation has been hacked should only be made when there is credible evidence, such as confirmation from:

  • the affected organisation;
  • a recognised cybersecurity authority;
  • credible security researchers; or
  • other reliable technical evidence.

Why This PHP Security Update Deserves Attention

Critical vulnerabilities are discovered regularly in software, but this incident deserves additional attention because the vulnerabilities exist in PHP itself rather than a single plugin, theme or website application.

PHP sits underneath WordPress, Drupal, Joomla and a huge number of custom web applications.

The combination of:

  • two critical vulnerabilities;
  • a CVSS score of 9.2;
  • potential unauthenticated remote code execution;
  • public technical information about the vulnerabilities; and
  • the widespread use of PHP

means organisations should treat patching as urgent.

For Sri Lankan organisations, the correct response is not panic or speculation about which websites may already have been hacked.

It is much simpler:

Identify internet-facing PHP systems, verify their patch status, update affected environments immediately, review systems for suspicious activity and keep additional protections such as a Web Application Firewall enabled.

Latest Update

The PHP project currently lists PHP 8.5.12, PHP 8.4.27, PHP 8.3.36 and PHP 8.2.35 as the security-fixed releases for the supported branches affected by these vulnerabilities.

Peak Lanka will update this article if there are significant new developments involving the vulnerabilities, major hosting platforms or confirmed impacts on Sri Lankan organisations.

Official and Technical Sources

This article provides general cybersecurity information based on publicly available security advisories. Peak Lanka has not performed intrusive security testing against Sri Lankan government or private-sector websites. Mentioning a technology, industry or type of organisation does not indicate that any specific website has been compromised.