Is Your Website Running on PHP? What PHP2Shell Means for Your Business
Yes, your website may well run on PHP, and a critical flaw called PHP2Shell means you should ask your web host about it today. PHP is the programming language that powers a huge share of business websites, including most WordPress sites, and the flaw lets a stranger take control of a server without a password. Fixes were released on October 21, 2026, and attackers started using the flaw the same day.
What is PHP, and why does it matter to a small business?
PHP is a programming language that runs on a web server and builds your pages each time a visitor asks for one. If your site runs on WordPress, or if an agency built it years ago and nobody has touched it since, there is a good chance PHP is working behind the scenes. You will not see it, because it lives on your host's server rather than on your computer.
That invisibility is the problem. Many owners in Fort Wayne, Auburn, Angola, and across northeast Indiana pay a monthly hosting fee and never learn what software their site depends on. A flaw this serious in the language itself puts every one of those sites in the conversation, whether or not anyone is paying attention.
What is PHP2Shell?
PHP2Shell is the name security researchers gave to two linked bugs in PHP. The NCSC, the United Kingdom's national cyber security agency, describes the problem as one that may allow attackers to run commands on any web server running PHP, and it urged organisations to act immediately.
In plain terms, the first bug (CVE-2026-109618) is triggered when PHP runs out of memory partway through handling a request and leaves its internal records half built. The second (CVE-2026-109619) happens when leftover data from one request survives and is wrongly used by the next one. Either can let an attacker run their own code on your server. Researchers call that "remote code execution," and it is about as serious as web security problems get, because the attacker can potentially take over the whole machine. Both bugs carry a CVSS v4.0 score of 9.2, which sits in the critical range.
How fast is this moving?
Faster than usual. According to watchTowr, the details leaked on social media on October 20, 2026, ahead of a planned disclosure on October 22. The PHP team responded by shipping an emergency release on October 21, and watchTowr's honeypot network, a set of decoy servers built to attract attackers, observed real exploitation starting that same day.
A leaked flaw with a published fix is the situation where attackers move quickest, because they can study the fix to learn what changed. For you, that means the gap between "a patch exists" and "your site has the patch" is the dangerous stretch.
Which versions of PHP are fixed?
The PHP project released updates for four branches: 8.5.12, 8.4.27, 8.3.36, and 8.2.35. If your host runs one of those numbers or something newer on the same branch, the fix is included.
Older versions are a harder story. Versions 7.4, 8.0, and 8.1 no longer get regular updates from the PHP project, so they depend on fixes from your hosting company's operating system or from a paid long-term-support vendor. PHP 7.3 and older, including the PHP 5 that some neglected sites still run, are affected and have no fix at all. The only real cure for those sites is moving to a supported version.
The flaw applies however the server runs PHP, including PHP-FPM, Apache mod_php, php-cgi, LiteSpeed, and FrankenPHP. Apache with mod_php carries the highest risk.
What are the three things to do today?
You do not need to read code for any of this. You need to make three requests and get answers in writing.
1. Ask your host which PHP version your site runs, and whether it has the fix. Send your hosting company a short message: "Is the PHP on my account patched for CVE-2026-109618 and CVE-2026-109619, and which version am I on?" Many managed hosts patch for you, but they still need to restart the PHP workers afterward for the fix to take effect. If the reply names 7.3 or older, ask for a move to a current version right away.
2. Check your WordPress side. In your WordPress dashboard, open Dashboard, then Updates, and install anything pending. Delete plugins and themes you no longer use, since each one is another door. If your host controls the PHP version, you can often see it under Tools, then Site Health, then Info.
3. Confirm you have a backup you have actually restored. A backup file that has never been tested is a hope, not a plan. Ask your host or developer when the last successful restore took place. If the answer is "never," schedule one on a copy of the site this week. If an attacker ever gets in, a clean, tested backup is how you recover fast.
Is there a quick workaround?
No. Researchers report no configuration setting that closes the hole. The only reliable response is to update PHP and restart the PHP workers.
What should you do if you think your site was already hit?
Signs of a break-in include pages you never wrote, redirects to unfamiliar sites, a host warning about malware, or sudden slowness. If you see any of them, tell your host immediately, change your passwords, and restore from a clean backup after the PHP update is applied. Restoring before patching just invites the attacker back.
How can Button Block and Hey Button help?
At Hey Button, our own sites are not built on PHP, so this flaw does not touch them. For the websites Button Block manages for clients, we verify the hosting setup and software versions as part of the work, and a flaw like this one goes straight to the top of the list.
If your site was built by someone else and you are not sure where it stands, we will run a free site check and tell you plainly what we find, with no pressure to hire us. You can start with a quick conversation, or see how a Hey Button AI teammate helps with the follow-up once your site is in good shape.
Sources: watchTowr PHP2Shell FAQ, UK NCSC advisory, Palo Alto Networks Unit 42, SiteGround.
Frequently Asked Questions
- Do I have to worry about PHP2Shell if my site is on WordPress?
- Yes, most likely. WordPress is built on PHP, so the PHP version on your hosting account decides whether you are exposed. Ask your host whether it has installed the October 21, 2026 fixes and restarted PHP, then update WordPress, plugins, and themes as usual.
- Can I fix PHP2Shell myself by changing a setting?
- No. Researchers report no configuration workaround. The fix is a PHP update followed by a restart of the PHP workers, which your hosting company usually performs. Your job is to confirm that it happened and to ask for a newer version if yours is too old.
- What if my site runs an old version like PHP 5 or 7.3?
- Those versions are affected and no fix exists for them. The safe path is to move the site to a supported PHP version, which may require your developer to test that your theme and plugins still work. Do not wait, since attacks are already underway.
- Is a free site check from Button Block really free?
- Yes. We look at how your site is hosted, which PHP version it runs, and whether obvious updates are missing, then tell you what we found in plain language. There is no obligation to hire us afterward, and we will say so if everything looks fine.
- How do I know if my site has already been attacked?
- Watch for pages you did not create, odd redirects, host warnings about malware, or sudden slowdowns. If you notice any of these, contact your host right away, change your passwords, and restore from a clean backup only after PHP has been updated.
Hey Button
Want a teammate that handles this for you?
Answer a few questions about your business and Hey Button will show you what an AI teammate would take off your plate, with you approving anything that goes out.




