News
PHP2Shell: what business owners need to know about this week's PHP flaws
Laelaps Security · · 5 min read
On October 21, 2026, the PHP project shipped emergency fixes for two critical vulnerabilities, now widely called PHP2Shell (CVE-2026-109618 and CVE-2026-109619). Both are rated 9.2 out of 10 for severity. Details leaked online before the planned release, and security firms have already seen attackers trying to use them.
If your business has a website, a customer portal, or an online store, there's a good chance PHP is running somewhere underneath it. Here's what happened, in plain terms, and what to ask your web host or IT provider today.
What is PHP, and why does this matter?
PHP is the programming language that powers a huge share of the web. WordPress, Drupal, Joomla, Magento, many online stores, and countless custom business tools are built on it. You may never have heard of it, but if you have a website, you probably rely on it.
Think of PHP as the kitchen staff in a restaurant. Visitors (the customers) send orders to your website, and PHP is the cook that prepares each response. Most of the time, the cook follows the recipe. These flaws are about what happens when the kitchen gets overwhelmed.
What's actually broken?
Both flaws come down to the same basic mistake: PHP doesn't always clean up after itself when a request fails partway through.
When PHP runs out of memory or hits a serious error in the middle of handling a request, it stops that request abruptly. The problem is that it can leave behind half-finished notes about what it was doing. On many servers, the same PHP "worker" then moves straight on to the next visitor's request, and it can pick up those stale notes and trust them as if they were valid.
Back to the kitchen: imagine a cook who drops an order halfway through, then starts the next one while the abandoned ingredients are still on the counter, and uses them without checking where they came from. An attacker who understands this can deliberately cause the "dropped order," leave carefully chosen "ingredients" on the counter, and then send a follow-up request that makes the server use them.
The result, in the worst case, is remote code execution: the attacker gets the server to run their own commands. That's why researchers named it PHP2Shell. "Shell" is security shorthand for control over a computer.
A few details make this one especially serious:
- No password needed. The attack works without logging in to anything.
- It happens before your website's own code runs. It doesn't matter how carefully your site was built. The flaw is in PHP itself, so even a simple page can be a way in.
- It's old and widespread. Researchers believe the problem goes back as far as PHP 5.4, released over a decade ago, and it affects the common ways PHP is run on web servers.
- AI made it easier to weaponize. The researchers who found it (from Wiz, OpenAI, and Calif) said modern AI tools substantially lowered the effort needed to turn these long-hidden bugs into a working attack. Expect to hear that more often.
To be fair to the defenders: pulling off full code execution is still technically tricky and depends on how a server is set up. Crashing a server or reading pieces of its memory is easier. But "tricky" stops mattering once someone publishes a working tool, and that's where we are.
What could an attacker do?
If an attacker takes over the server behind your website, they can typically do whatever the website itself can do. Depending on your setup, that might mean:
- Reading customer records, form submissions, or order history
- Stealing database passwords or other credentials stored on the server
- Defacing your site, or quietly adding malware that infects your visitors
- Using your server as a foothold to reach other systems
For healthcare, legal, and defense-related businesses, any of these can also become a reportable incident with regulatory consequences.
What should you do now?
1. Find out what version of PHP you're running. If you use a hosting company, the version is usually shown in your hosting control panel (look for "PHP version" or "MultiPHP Manager" in cPanel). If someone else manages your site, ask them directly.
2. Make sure it's updated to a fixed version. The patched releases are:
- PHP 8.5.12
- PHP 8.4.27
- PHP 8.3.36
- PHP 8.2.35
Anything older than these in the same line is vulnerable. PHP 8.1 and earlier no longer get official updates. If you're still on one of those, this is the moment to move to a supported version, or confirm that your host or Linux vendor is providing a backported fix.
3. If you're on shared or managed hosting, ask your host. On most shared hosting, the hosting company updates PHP for you, but don't assume. Send them a short note: "Have you applied the PHP2Shell fixes (CVE-2026-109618 and CVE-2026-109619) to the servers hosting my site?" Get a yes in writing.
4. If you can't patch right away, reduce the risk. A web application firewall (WAF) can block known attack patterns. Cloudflare has released protections, including on its free plan, and other WAF vendors have too. Your IT provider may also be able to switch off two PHP features the known attacks lean on (session upload progress and OPcache) as a temporary measure. None of these replace the update. The UK's National Cyber Security Centre has gone further and advised taking offline any system that can't be fixed promptly.
5. Look for signs of trouble. Because attacks started before many sites were patched, it's worth having your IT provider check for warning signs: unexpected files on the server, unfamiliar programs running, unusual outbound connections, or a spike in PHP memory errors and crashes in the server logs.
The bigger lesson
PHP2Shell is a reminder that your security depends on software you didn't write and may not know you're running. The businesses that handle events like this calmly have three things in place:
- An inventory. They know which websites and systems they have, and what they run on.
- A patching process. Someone owns updates and can move fast when a critical fix lands.
- A plan. They've decided in advance who to call and what to do if something gets through.
If you're not sure where your business stands on any of those, that's exactly the kind of question we help with. Book a free 30-minute consultation and we'll help you work out what you're exposed to and what to fix first.