← Back to the blog AI Consulting · Toledo, Ohio

A PHP Flaw Hit Millions of Websites This Week. Ask Your Host Which PHP Version You Run.

Jayson Hines · October 23, 2026 · 4 min read

PHP shipped emergency patches Wednesday for two flaws, CVE-2026-109618 and CVE-2026-109619, and both are rated 9.2 out of 10. They let an attacker run their own code on your web server without ever logging in. Finland, the Netherlands, Belgium, and France pulled government sites offline, some of it as a precaution, and the FBI and NSA said to take systems offline if you can't update fast.

If you've never heard of PHP, that's normal. Most owners I work with haven't. It's the software sitting underneath a huge number of websites, and that includes anything built on WordPress. Your web person set it up years ago and it's been quietly running on your host's server ever since. Palo Alto Networks counted more than 22.6 million internet-connected setups that could be affected. That's not the same as 22.6 million websites, but it's a big number for something most people couldn't point to.

Why this is an AI story

OpenAI said AI tools helped find these bugs, and that it worked with security firms to get fixes ready before anything went public. Good for them. But anything that helps the people fixing holes find them faster helps the people breaking in too, and the gap between a hole being found and someone using it keeps getting shorter. Cloudflare reported attack traffic within days, including attempts to get around its protections. It didn't say any of them worked.

I tell people in my workshops that AI makes the other side faster, not just yours. This is a clean example of it. A small business can't out-watch that. What you can do is make sure somebody is keeping the boring stuff updated.

Updating your plugins won't fix this

This is the part that trips people up. The flaw is in PHP itself, so updating WordPress and your plugins doesn't touch it. The PHP version is a setting on your hosting account, and the fixes are out for versions 8.2 through 8.5. If you're on something older, you may not get a fix at all and you'll have to move up to a supported version. Moving up can break an old plugin or theme, so don't flip it at 4pm on a Friday without a backup.

One piece of good news from the reporting: just visiting an affected site doesn't infect your customers' devices. The risk is to your site and your server, which is bad enough if it's the thing taking your bookings.

The twenty minute check

Open a support ticket with your web host, or email whoever built your site, and ask three plain questions. What PHP version is my site running? Has it been patched this week? If it's old, can you move me to a supported version? Make sure you have a fresh backup before anyone changes anything.

Then think about the forgotten stuff. The old landing page from a campaign two years ago, the booking tool on a subdomain, the site you built for a side project. Those are the ones sitting on a PHP version nobody has touched since launch day. Ask your host to list everything on your account so you can see what's actually there.

If your host can't tell you the version or won't upgrade it, that's your answer about whether to stay with them. Plenty of Toledo businesses are paying twenty bucks a month for hosting that nobody's watching, and this week showed what that costs.

I run AI workshops and one-on-one AI consultations for companies around Toledo, Northwest Ohio, and Southeast Michigan, and a big part of that is helping owners figure out what's actually running under their business and who's watching it. If you'd like a second set of eyes on your website setup or your team's tools, send me a note.

Email Jayson