Website Security: How Webnames Handles New Vulnerabilities - Webnames Blog

Website Security: How Webnames Handles New Vulnerabilities

Software has security flaws. Operating systems, programming languages, content management systems, plugins: all of it gets picked over constantly by developers, security researchers and, yes, people trying to break in.

PHP is the latest example. Two vulnerabilities, CVE-2026-109618 and CVE-2026-109619, were assigned a Critical CVSS 4.0 score of 9.2. Security releases addressing the vulnerabilities were released on 21 October 2026: PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12.

PHP runs a huge number of websites, including WordPress sites, and it’s available across our hosting environment. We deployed the patched releases to our hosting servers shortly after they came out. Our website, DNS and email services don’t use PHP, so they weren’t affected.

For customers using older versions of PHP, the situation is a little different, and it’s worth understanding why.

A vulnerability doesn’t mean your site was hacked.

When a “critical vulnerability” hits the news, it’s natural to worry. But a vulnerability is a weakness that could be exploited under certain conditions. It isn’t proof that every site running the affected software has been compromised.Anonymized hacker sitting with a laptop

Once a vulnerability becomes public, developers, researchers, hosting providers and security vendors assess the risk and decide how to respond. Sometimes that’s installing an update. Other times, additional protective measures can help mitigate the threat where an immediate update isn’t possible.

New vulnerabilities will keep turning up. What matters is how quickly they’re caught, contained and fixed, and what other protections are already in place.

PHP versions have a lifecycle

Like most software, PHP versions don’t remain supported indefinitely. A major PHP release is supported for a defined period during which it receives bug and security fixes. Eventually it reaches End of Life (EOL), after which the PHP project no longer provides updates for that release.

As of October 2026, PHP 8.2, 8.3, 8.4 and 8.5 remain supported by the PHP project. PHP 8.1 and all earlier versions have reached EOL.

PHP versionReleasedEnd of life
5.628 Aug 201431 Dec 2018
7.03 Dec 201510 Jan 2019
7.11 Dec 20161 Dec 2019
7.230 Nov 201730 Nov 2020
7.36 Dec 20186 Dec 2021
7.428 Nov 201928 Nov 2022
8.026 Nov 202026 Nov 2023
8.125 Nov 202131 Dec 2025
8.28 Dec 202231 Dec 2026
8.323 Nov 202331 Dec 2027
8.421 Nov 202431 Dec 2028
8.520 Nov 202531 Dec 2029

The PHP project recommends that users of EOL releases upgrade to a current version because older releases may be exposed to security vulnerabilities and bugs fixed in newer versions.

That’s particularly relevant to the current vulnerabilities. Official corrected releases were issued for supported PHP 8.2 through 8.5, but PHP 8.1 and earlier did not receive new official PHP releases.

This doesn’t mean a website stops working when its PHP version reaches EOL. It means that continuing to work and continuing to be supported are two different things.


Why can I still select an End-of-Life PHP version?

Webnames offers a range of PHP versions, including some that have reached End of Life, to maintain compatibility with older websites.

We don’t automatically change the PHP version assigned to your website. Websites and applications need to be coded and tested for compatibility with specific PHP versions, and changing versions without testing can cause a website to stop working or behave unexpectedly.

Older PHP versions are therefore available for compatibility, not because they remain recommended for ongoing use. If your website requires an End-of-Life PHP version, we recommend working with your web developer to update its code and test it with a currently supported version of PHP.


What if my website needs an older version of PHP?

We know that some older websites depend on older PHP versions and can’t simply be switched to a current version without changes to their code.

Webnames has additional security controls protecting our hosting environment. For the current CVE-2026-109618 and CVE-2026-109619 vulnerabilities, our Imunify and firewall Intrusion Prevention System (IPS) protections are blocking attempts to exploit these vulnerabilities at the security layer. This provides important mitigation for customers whose websites are currently running versions of PHP for which an official updated PHP release isn’t available.

But there’s an important distinction: mitigation isn’t the same thing as patching the underlying software.

A WAF, IPS or other security control can provide an additional barrier against a particular known attack. It doesn’t turn an EOL version of PHP into a supported one, nor can we guarantee that every future PHP vulnerability will have an effective external mitigation.

That’s why we recommend that customers running an EOL version of PHP speak with their web developer about moving their website to a currently supported PHP version.

That doesn’t necessarily mean redesigning or replacing the website. Depending on how the site was built, a developer may be able to update its underlying code, components or configuration to make it compatible with a newer PHP version while leaving the appearance and content of the site substantially unchanged.

The important objective is to keep the software underneath the website maintainable.


Not sure which version of PHP your website uses?
The PHP version currently assigned to your website is displayed in your Webnames Hosting Control Panel. This is the version your website is presently configured to run on.


No single tool does it all.

No firewall or product can stop every threat, so we don’t rely on just one. We use several overlapping protections, an approach often called “defence in depth.” Each one covers different risks.

PHP and the hosting platform. We run our web hosting services on Plesk and offer a range of PHP versions to accommodate different websites and applications. For PHP versions currently supported by the PHP project, we maintain the latest patched releases so that security fixes can be applied at the hosting-platform level without individual customers having to maintain the PHP installation themselves.

For EOL PHP versions, Webnames’ other security layers can continue to provide valuable protection, but customers should plan to transition their websites to a supported PHP version.

That only covers PHP, though. The software running on top of PHP is a separate matter. A WordPress plugin can have a vulnerability even when PHP itself is fully patched.

Web application firewall. Our hosting environment is protected by Imunify, including a Web Application Firewall (WAF), together with firewall IPS protections.

These technologies provide another layer between Internet traffic and customer websites, helping us identify and block malicious activity and attempts to exploit vulnerabilities.

For the current PHP vulnerabilities, these protections are also allowing us to mitigate CVE-2026-109618 and CVE-2026-109619 for customers whose sites still depend on older PHP versions.

Imunify also provides malware and malicious PHP-script detection as another layer of defence.

Vulnerability detection in website applications. We also run Patchman. Updating PHP and the server protects the platform, but vulnerabilities can also live in the applications themselves. Patchman detects vulnerabilities and malware in widely used content management systems such as WordPress, Joomla and Drupal, and can apply security patches for supported vulnerabilities.

Extra tools for WordPress. A WordPress site is more than WordPress. Your themes and plugins are part of the application too, and they need to stay patched. All three of our Managed WordPress hosting plans include the standard edition of Plesk WP Toolkit. It covers security checks and hardening, automatic updates, plugin and theme management, staging, cloning and synchronisation, and maintenance and debugging tools. It makes it easier to keep the WordPress side of things secure, on top of the protections we run at the platform level.

Backups. Prevention is only part of security. You also need a way to recover if something goes wrong. We back up our hosting servers and customer websites so we can recover from a total server failure. Customers on any hosting plan other than Value also get two weeks of daily backups in their Hosting Control Panel and can restore from them when needed.

Backups aren’t a substitute for prevention. Restoring an older copy of your site doesn’t fix whatever let the problem happen in the first place.

Security is a shared job.

We look after the hosting infrastructure: the server platform, supported PHP installations and the security tools around your site. You control the software and content inside your own website, so keeping it secure takes both of us.

Website owners should:

  • keep WordPress, Joomla, Drupal and other applications up to date
  • update plugins, themes, modules and extensions
  • remove software they’re no longer using
  • avoid plugins, themes and other software that are no longer actively maintained
  • use strong, unique passwords for website administration
  • turn on multi-factor authentication wherever the application supports it
  • limit administrative access to the people who need it
  • look into any unexpected changes to website files, content or admin accounts

Updating PHP fixes vulnerabilities in PHP. It can’t fix a flaw in a WordPress plugin, a custom PHP application or anything else you’ve installed yourself.

AI is changing security for attackers and defenders.

AI is changing how software gets written and analyzed. The same tools that help developers and researchers find weaknesses in code can help attackers find them too, Business team working in a glass-walled meeting roomand automate parts of their work.

So AI-assisted research may mean vulnerabilities are found faster and in greater numbers. But defenders have the same tools. Developers, researchers and security vendors can use AI and automation to analyse vulnerabilities and malicious activity and build defences more quickly.

The upshot is that you may hear about vulnerabilities more often. That doesn’t necessarily mean software is getting less secure. Better tools can surface flaws that might have gone unnoticed for years, and faster disclosure, monitoring, mitigation and patching shorten the time a known vulnerability stays open.

Vulnerabilities will keep showing up.

No hosting provider, developer or security vendor can honestly promise there won’t be another one. A modern website depends on a lot of connected pieces: operating systems, web servers, databases, programming languages, content management systems, plugins, themes, libraries and custom code. All of them change over time, and any of them can have flaws.

So good security doesn’t assume vulnerabilities can be eliminated. It assumes they’ll happen and plans for it: prevent what you can, detect what you can’t, mitigate new threats, patch known problems, and keep reliable backups. That’s how we run our hosting environment.

What Webnames’ customers need to do about the PHP vulnerabilities.

If your website uses a currently supported version of PHP: you don’t need to update the PHP installation provided by your Webnames hosting service yourself. We deployed the applicable patched releases after they became available.

If your website uses an EOL version of PHP: Webnames’ Imunify and firewall IPS protections are currently providing mitigation against CVE-2026-109618 and CVE-2026-109619. However, we recommend speaking with your web developer about updating your website so that it can operate on a currently supported PHP release.

There’s no need to assume that an older website must immediately be replaced or completely redesigned. But if its underlying code prevents it from running on supported software, modernising that code should become part of the site’s maintenance plan.

And please don’t assume that a vulnerability headline means your site has been compromised. Take security news seriously, but keep it in perspective. Finding, mitigating and patching vulnerabilities is a normal, ongoing part of running anything on the Internet, and we plan for that.

Share this:

Posted in:

Security