23 Oct PHP2Shell Has Cracked the Engine Under Most Business Websites – Here’s What Businesses Need to Do
A critical flaw called PHP2Shell was disclosed on October 21, 2026. It affects the engine underneath WordPress, WooCommerce, and most of the web. Here's what it means for your business, in plain English.
Last Tuesday, a business owner in Appleton opened her laptop to find her WooCommerce store had been taken offline by her hosting company. No warning. No explanation at first. Just a message that her server had been suspended due to "suspicious activity." She hadn't changed a thing on her website. Her plugins were up to date. She had a security plugin installed. She thought she'd done everything right.
What she didn't know, and what most business owners don't yet know, is that a critical security flaw was discovered this week in the programming language that powers her website. Not in WordPress. Not in her plugins. In the engine underneath all of it. That engine is called PHP, and the flaw is called PHP2Shell.
What Is PHP2Shell? Three Terms Explained
Before we go further, here are the only three technical terms you actually need to understand this story.
Plain-English Glossary
PHP
The programming language that runs the server-side of most websites, including WordPress, WooCommerce, Drupal, and Joomla. Think of it as the engine under your website's hood. You never see it, but it's doing the work every time someone visits your site.
Remote Code Execution (RCE)
When an attacker can run commands on your server from anywhere on the internet without logging in. Imagine someone being able to sit at the keyboard of your server from their couch in another country. That's RCE.
CVSS 9.2 out of 10
The official severity score for PHP2Shell. Scores above 9.0 are classified as "Critical," a designation reserved for flaws that are easy to exploit, require no authentication, and can cause serious damage. For context: Heartbleed, one of the most-discussed internet security events of the last decade, was a 7.5.
PHP2Shell Is a Flaw in the Engine Itself, Not Your Plugins or WordPress
PHP2Shell is the name for two bugs discovered in PHP itself, not in any app, plugin, or piece of code that runs on top of PHP. The bugs are officially tracked as CVE-2026-109618 and CVE-2026-109619. They were found by researchers at security firms Wiz and OpenAI, disclosed publicly on October 21, 2026, the same day PHP developers released emergency patches.
Here's the analogy that makes this clearer than any technical explanation: imagine your office building has a structural crack in its foundation. It doesn't matter how well-maintained the offices are inside. It doesn't matter that you change the locks every year and install the best security cameras. A crack in the foundation means someone can get in regardless of all that because they're not going through the door.
That's what's different about PHP2Shell. Patching WordPress doesn't fix it. Updating your plugins doesn't fix it. Running a security scanner doesn't fix it. The fix has to happen at the foundation, in PHP itself.
In plain terms: what an attacker can do
A successful PHP2Shell attack gives the attacker full control of your web server. They can read your customer database, install malware, create hidden back doors for future access, send spam from your domain, and take your site offline, all without your username or password. One of the two flaws also leaks server memory that can expose passwords and API keys from other websites sharing the same server.
"PHP2Shell is likely the most serious PHP vulnerability ever published. It's a flaw in PHP itself. Every PHP-based site is potentially affected."
Does PHP2Shell Affect WordPress, WooCommerce, and Other Platforms?
If your website is built on a PHP-based platform, it's in scope. That includes the platforms used by the vast majority of Wisconsin small businesses, whether you're running a law firm, a manufacturer, a restaurant, or a retail store.
- ⚠ WordPress
- ⚠ WooCommerce
- ⚠ Drupal
- ⚠ Joomla
- ⚠ Magento
- ⚠ Shopware
- ⚠ Laravel apps
- ⚠ Custom PHP sites
- ✓ Shopify
- ✓ Squarespace
- ✓ Wix
- ✓ Static HTML only
Shopify, Squarespace, and Wix are fully managed platforms. They handle their own server infrastructure and any patching that's needed. If your site is on one of those, you don't need to do anything for PHP2Shell specifically. For everyone else, keep reading.
How Fast Is PHP2Shell Spreading and Why Waiting Is Risky
Most security vulnerabilities take weeks or months before attackers start using them. PHP2Shell was different. Within 45 minutes of the patches being released on October 21, Cloudflare had already logged tens of thousands of attack attempts. Within 24 hours, that number had climbed into the millions. Researchers at Amazon found evidence of test attempts as early as October 17, before the flaw was even announced publicly.
The reason this moves so fast is automation. Attackers don't sit at a keyboard picking targets one by one. They run automated tools that sweep the entire internet looking for servers running unpatched PHP. If your server shows up in that scan and it's unpatched, it gets added to a list, regardless of how small your business is, what industry you're in, or whether you think anyone would bother with you.
As of today, October 23, researchers estimate that more than 34 million servers are still running unpatched PHP versions. Patches exist for PHP 8.2.35, 8.3.36, 8.4.27, and 8.5.12. No patch exists for PHP 7.4, 8.0, or 8.1. Those versions are past their end-of-life, and upgrading is the only option.
What "end-of-life" means for your website
If your site runs PHP 7.x or an older PHP 8.x branch, there is no official security patch for PHP2Shell, and there won't be one. Your only option is to migrate to a supported PHP version. This is now an emergency-tier item, not a scheduled upgrade.
How to Protect Your Website from PHP2Shell: Your 72-Hour Checklist
Here's what to do, broken down by how quickly each item needs to happen. You don't have to understand everything about PHP to work through this list. You just need to know who manages your website and be willing to ask a direct question.
Do today (within 24 hours)
-
Find out what PHP version your website runs.
Contact your web host or IT provider and ask: "What PHP version is our website running right now?" The safe versions are 8.2.35, 8.3.36, 8.4.27, and 8.5.12. Anything below those numbers is unpatched.
-
Ask your web host if they've applied the PHP2Shell patch.
Many managed hosts have already patched their servers. Get a specific PHP version number in their response, not just "we're on it" or "we're working on it." If they can't tell you the version, escalate.
Do this week (within 72 hours)
-
If you can't patch immediately, ask about temporary mitigations.
A configuration change called session.upload_progress.enabled = Off blocks one of the two confirmed attack paths. Ask your host or IT provider to apply it. It's not a permanent fix, but it reduces exposure while the patch is being applied.
-
Look for anything unusual on your website.
Check for new unfamiliar admin accounts, new files you didn't create, or pages that look different than expected. If something seems off, don't try to clean it up yourself. Call your IT provider or hosting company first.
-
If your site runs PHP 7.x, 8.0, or 8.1, treat this as an emergency.
No patch exists for these versions. An upgrade to PHP 8.2 or later is your only option and should be scheduled as an emergency project, not a routine maintenance item.
This month (once you're patched)
-
Ask your IT provider about ongoing PHP version monitoring.
PHP releases security updates regularly. Knowing what version you're on and getting notified when it's out of date is something your IT provider should be tracking for you automatically.
-
Request a server log review if you're not sure whether you were targeted.
Your hosting company or IT provider can review server logs for signs that automated tools probed your site during the high-activity window of October 21–22. This doesn't mean you were compromised, but it tells you whether to look more carefully.
Not sure where your business stands? We can find out for you.
Focus Systems helps businesses across Appleton, Green Bay, Oshkosh, and the Fox Valley manage and secure their IT environments. Here's what we can do for you right now:
- Identify what PHP version your servers and applications are running
- Confirm whether the PHP2Shell patches are in place and close any gaps
- Review server logs and web files for early signs of compromise
- Coordinate with your hosting company or handle the update directly
- Put monitoring in place so the next critical PHP release doesn't catch you off guard
Start with a free IT Health Check. We'll give you a clear picture of where you stand.
Claim your free IT Health Check
Or call us: 920-870-0002
PHP2Shell FAQ: Questions Wisconsin Business Owners Are Asking
Does a WordPress security plugin protect against PHP2Shell?
Not for this. WordPress security plugins run on top of PHP. They're part of the engine's passengers, not the engine itself. PHP2Shell targets the engine directly, before any plugin or application-level code has a chance to run. The only fix is patching PHP itself.
Will attackers target a small or inactive business website?
Yes, because the attacks are automated. Automated tools don't pick targets based on how active or interesting a website is. They scan IP addresses looking for unpatched PHP versions. If yours shows up in that scan, it goes on the list. A dormant site is often easier to compromise than an actively maintained one, because no one's watching it.
Has PHP2Shell been actively exploited yet?
As of October 23, millions of automated attack attempts have been recorded, and some organizations pulled their own websites offline as a precaution rather than risk exposure. No mass confirmed compromise affecting small businesses has been publicly reported yet, but security researchers describe the window before reliable large-scale exploitation as short. Patching now is significantly better than waiting to see what happens.
Can I patch PHP2Shell myself, or do I need an IT provider?
If you have access to your hosting control panel and it allows you to switch PHP versions, you can ask your host to upgrade you to a patched version. However, switching PHP versions can sometimes break website functionality, especially for older sites, so it should be tested rather than flipped on a live site without preparation. For most business owners, this is something to hand to your hosting company or IT provider.
Which PHP versions are patched and safe from PHP2Shell?
The patched versions are PHP 8.2.35, 8.3.36, 8.4.27, and 8.5.12 or any newer release in those branches. PHP 7.x, 8.0, and 8.1 have no official patch and won't get one because those versions are past their end-of-life. Sites still on them need to migrate to a supported PHP 8 branch.
What if my hosting company or web developer hasn't heard of PHP2Shell?
That's a yellow flag. PHP2Shell was widely covered in the technical press within hours of its disclosure. Your hosting company should have been monitoring this and either already patched or actively working through it. A developer or host who isn't aware of a CVSS 9.2 critical vulnerability in the core infrastructure they manage for you is worth a serious conversation about service expectations.
Is PHP2Shell a Wisconsin-specific problem or does it affect everyone?
No. PHP2Shell affects servers worldwide. We're writing about it from a Wisconsin perspective because that's who we serve, but the vulnerability itself doesn't discriminate by geography. Millions of attack attempts have been recorded across North America, Europe, and Asia.
What is the first step to protect my business from PHP2Shell?
Call or email whoever manages your website and ask them what PHP version you're on and whether it's been patched for PHP2Shell. That one conversation tells you everything you need to know about whether this is urgent for you specifically.
Sources
- PHP2Shell Exploit Attempts Hit Millions as Attackers Try to Deploy Mirai Malware, The Hacker News, October 23, 2026
- CVE-2026-109618 and CVE-2026-109619: PHP Vulnerable to Unauthenticated RCE Attacks, Zscaler Security Research
- PHP2Shell: PHP RCE (CVE-2026-109618, CVE-2026-109619), Sansec
- Rapid Response: php2shell, Leaked Critical PHP Vulnerabilities, Huntress
- PHP2Shell: Find, Mitigate, and Patch Now, Qualys Threat Research Unit
- CrowdStrike Protects Customers from Threats Delivered via PHP2Shell, CrowdStrike
- PHP2Shell: Critical PHP Vulnerabilities Patched: Update Now, Help Net Security, October 21, 2026
- Cloudflare deploys protections against PHP2Shell vulnerability, Cloudflare, October 21, 2026
- PHP Shell Vulnerability: What It Is and How to Fix It, IT Extremes
- PHP Official Security Releases, October 2026, PHP.net
Let Focus Systems take this off your plate.
Not sure if your website is patched? Our free IT Health Check gives you a clear, jargon-free picture of your current security posture and what to do about it.