A serious website security issue prompted organizations around the world to take immediate action this week, with even government websites in France, Denmark, Finland, and the Netherlands temporarily taken offline as a precaution. The issue, known as PHP2Shell, involves two critical vulnerabilities in PHP, the engine that powers WordPress and many other website platforms, which could allow attackers to run commands on vulnerable servers without even logging in.
Yesterday, we updated PHP to version 8.2.35 on all of our servers. This version has emergency fixes for two critical vulnerabilities: CVE-2026-109618 and CVE-2026-109619 (known as PHP2Shell). PHP was patched, restarted, and is now running a release that contains the fixes for both vulnerabilities. Our servers are up to date against this threat, as the security of our sites and our clients has always been a top priority for us.
A Flaw in the Software About 70% of Websites Run On
If your law firm relies on its website to reach prospective clients, you want to know that the website is working properly and that the information people submit through it is protected. Unfortunately, a website can appear to be functioning exactly as it should while the software running underneath it has a serious security problem.
According to W3Techs, PHP runs on 69.3% of websites whose server-side programming language it can identify. WordPress is one of the many platforms that depend on PHP, which means a vulnerability in PHP itself can affect far more than one website, theme, or plugin.
The primary concern with PHP2Shell is something called remote code execution, or RCE. Essentially, this means an attacker could cause a vulnerable server to run commands of their choosing without first having to log in.
Depending on how the server is configured and what permissions are available, an attacker could potentially change website files, access sensitive information, or interfere with the systems that process your intake forms.
What Happened, In Order
Taking a look at when information became public, when the fixes became available, and when attack activity was first observed can help illustrate why this update required immediate attention. Here’s a quick timeline:
- October 17: Amazon Threat Intelligence later identified a PHP2Shell exploitation attempt against its MadPot honeypot network, four days before the fixes were publicly released.
- October 20: The vulnerability identifiers began circulating online ahead of the planned disclosure.
- October 21: PHP released the emergency fixes. The release had originally been scheduled for October 22, but was moved forward one day in response to the leak.
Importantly, the October 17 finding indicates that an apparent threat actor had information about exploiting these vulnerabilities before the public advisory and before the patches were generally available. This means that the risk existed before many website owners would have known to ask about it.
Why Updating WordPress Does Nothing Here
If you have access to your WordPress dashboard, you are most likely familiar with the notifications asking you to update WordPress, your plugins, or your theme. These updates are an important part of maintaining your website; however, they don’t replace the PHP software that is running on your server, which means completing them doesn’t resolve this particular problem.
There are three primary layers to understand here.
Your Website: WordPress, Plugins, and Themes
This includes the parts of your website you are probably most familiar with, such as WordPress itself, the plugins used for contact forms, and the theme that controls how your website looks. When you update these components, it addresses issues within those components, but it does not update every piece of software your website depends on.
The PHP Runtime
PHP runs the instructions that allow your WordPress website to function. Since PHP2Shell affects this underlying engine, a website can have the latest WordPress updates installed and still be running on vulnerable PHP software. The PHP installation itself needs the fix.
The Supplier
Generally, your hosting company or server administrator installs PHP through packages supplied by a software distributor or vendor. Some hosting dashboards allow you to select a PHP version yourself, but your provider still needs to make a patched build available. WordPress also directs users to their hosting settings or provider when updating PHP.
This means that, for most law firms, the hosting provider plays an essential part in addressing the problem; someone needs to be responsible for the software underneath your website, and that company should be able to tell you which version is actually running.
How to Check Your Own Site in About Two Minutes
If you have administrator access to WordPress, checking your PHP version is fairly straightforward. You can do so by taking the following steps:
- Sign in to your WordPress dashboard.
- Open Tools → Site Health.
- Select the Info tab.
- Expand Server.
- Locate PHP version.
The first releases containing the fixes for the supported PHP branches are as follows:
- First release containing the fixes for PHP branch 8.5: 8.5.12
- First release containing the fixes for PHP branch 8.4: 8.4.27
- First release containing the fixes for PHP branch 8.3: 8.3.36
- First release containing the fixes for PHP branch 8.2: 8.2.35
When comparing your version, you need to look at the fixed release within the same branch. If your website is running PHP 8.1 or older, you should contact your provider immediately, as these branches no longer receive regular official PHP releases.
However, some vendors provide backported fixes, and the PHP security team also supplied limited source backports for certain older branches. Therefore, seeing an older version means you need additional information from your provider before determining whether the fix has been applied.
Six Questions to Ask Your Hosting Provider Today
1. Is the PHP build serving my site patched for CVE-2026-109618 and CVE-2026-109619?
A good answer: Your provider confirms that both vulnerabilities have been addressed and supplies the exact release or vendor package identifier, along with the relevant security advisory.
What should worry you: A statement such as “we’re fully patched,” without explaining which software was checked or confirming that the answer applies to the server running your website.
2. What exact PHP version and build date is my site running right now?
A good answer: Your provider gives you the specific version and build information for the PHP installation that is actually handling your website’s traffic.
What should worry you: A general answer about the hosting platform, or a version shown in a control panel without confirmation that your website uses it.
3. If you backported the fix, which package version contains it, and can I see the changelog entry or advisory naming both CVEs?
A good answer: Your provider identifies the vendor package and provides documentation showing it contains the fixes for both vulnerabilities.
What should worry you: A claim that older versions are secure without any documentation allowing you to verify that the necessary fixes were applied.
4. When did you restart PHP workers after applying the update?
A good answer: Your provider gives you a recorded restart or replacement time and confirms that the processes serving your website are now using the patched build.
What should worry you: An answer confirming that the update was downloaded or installed, but failing to confirm that the running service is using it.
5. My site is on PHP 8.1 or older. What is your plan, and when?
A good answer: Your provider documents a fix for the current build, where one is available, and gives you a specific plan for moving to a supported PHP branch. This should also include checking that your website will work properly with the newer version.
What should worry you: An open-ended promise to upgrade at some point in the future, or a claim that older PHP versions cannot be affected by these vulnerabilities.
6. Did you use the partial php.ini mitigation while awaiting the patch, and do you understand its limits?
A good answer: Your provider explains whether disabling session upload progress was used temporarily and confirms that patching followed. This setting blocks confirmed session attack paths, but other variants remain. If a patched build is already running, not having used this temporary measure does not, on its own, mean the fix is incomplete.
What should worry you: An answer treating a configuration change as though it fully replaces the security update.
If You Don’t Get a Straight Answer
You should be able to find out whether your website received an emergency security fix without having to become an expert in server administration. Your provider should be prepared to explain what changed, when the work was completed, and whether anything remains under review.
If you have not heard from your hosting provider, you should ask. If you have specific questions and continue receiving vague answers, your firm is left without the information it needs to understand how its website is being maintained.
When you pay someone to maintain the environment your website depends on, you are also relying on that person or company to respond when an emergency falls outside the normal update schedule. Sometimes, that means work needs to happen outside ordinary business hours.
Applying this update was part of that obligation to our clients. We updated PHP across our servers and restarted it to put the fix into use. If you are unsure who handles this work for your firm, you can contact Accel Marketing Solutions to discuss your website and hosting needs.