Managed IT · Oct 21, 2026
PHP2Shell: critical PHP vulnerabilities and why your website needs patching now
On October 20, details of two critical vulnerabilities in PHP leaked publicly before fixes were available. The security firm Huntress dubbed them PHP2Shell. They are tracked as CVE-2026-109618 and CVE-2026-109619, and both carry a CVSS severity score of 9.2 out of 10.
On October 21, the PHP project released fixed versions: 8.5.12, 8.4.27, 8.3.36, and 8.2.35. According to Huntress, PHP 8.1 and older versions do not receive an official fix.
If that sounds like developer news, here is why it is business news. PHP runs a huge share of the web, including WordPress, Drupal, and Joomla. If your company website runs on one of those, it almost certainly runs on PHP.
How the vulnerabilities were found
OpenAI says the vulnerabilities were found as part of a coordinated disclosure effort it calls Patch the Planet, which uses AI to find security flaws in widely used software and report them to maintainers. The details leaked before the planned disclosure, which is why there was a gap between public knowledge and available patches.
This is part of a trend we have been watching all fall. AI models are getting very good at finding software vulnerabilities. Anthropic, Google, and OpenAI have all talked about it this year. That is good news for defenders, and it means attackers have the same capability.
Why small business websites are at risk
Most small business websites are not attacked because someone targeted the business. They are attacked because automated scanners find a vulnerable version of common software and exploit it at scale.
A compromised website can be used to host malware, steal form submissions, redirect visitors to scams, or serve as a foothold for further attacks. The business often finds out when Google flags the site or a customer complains.
What to do this week
- Find out what PHP version your website runs. Your hosting provider's control panel usually shows it. If someone else manages your site, ask them directly.
- Update to a fixed version. If you are on 8.2 through 8.5, move to the patched release for your version.
- If you are on PHP 8.1 or older, plan an upgrade. There is no official fix. You may need to update your website platform and plugins to support a newer PHP version.
- Update WordPress, Drupal, or Joomla and all plugins. Old plugins often block PHP upgrades.
- Check with your host. Many managed hosts patch PHP automatically. Confirm rather than assume.
- Watch for signs of compromise. Unexpected admin users, new files, or strange redirects are all warning signs.
The bigger lesson
Websites tend to get built, launched, and forgotten. Nobody owns updates. That works until a vulnerability like this one appears, and then nobody knows what version is running or who has the login.
Every business website should have a named owner for updates, a record of where it is hosted and who has access, and a regular patch schedule.
What this means for your business
- If your website runs WordPress, Drupal, or Joomla, it runs PHP and may be affected.
- Fixed versions are available for PHP 8.2 and newer. Older versions need an upgrade.
- AI is speeding up vulnerability discovery, so patching cadence matters more every year.
- Make sure someone is responsible for keeping your website updated.
Keeping websites and servers patched is part of what our Managed IT team handles. If you are not sure what your site is running, we can take a look.
