What changed
On October 21, PHP released emergency security updates to fix CVE-2026-109618 and CVE-2026-109619, two critical vulnerabilities rated 9.2 out of 10 that allow attackers to execute code remotely on web servers. The flaws affect every PHP version from 5.4 through 8.x, which powers an estimated 70% of websites worldwide, including those built on WordPress, Drupal, and Joomla.
The vulnerabilities leaked online on October 20, a day before the scheduled fix, and exploits began circulating immediately. Cloudflare reported attack attempts as early as 7:43 a.m. UTC on October 21, hours before the patch was available. Security researchers confirmed that attackers could gain access without logging in, even before any application code runs. Fixed versions are PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35. PHP versions 8.1 and earlier will not receive patches.
What you can do with it this week
If your website, online store, or booking system runs on PHP, update it today. Don't wait until Monday. Check your hosting control panel, contact your hosting provider, or ask your developer to confirm you're running a patched version. If you use WordPress, Drupal, Joomla, Magento, or Shopify on a managed host, they may have already patched it—but verify.
If you're on a shared hosting plan and can't update PHP yourself, email your hosting company right now and ask if they've applied the October 21 patches. If they say no or don't reply within 24 hours, consider moving your site to a host that responds to security emergencies. This isn't the last one.
If your site is on PHP 8.1 or earlier, you have no patch. Your only option is to upgrade to PHP 8.2 or newer. If your developer says your site won't run on PHP 8.2, you have two choices: pay them to fix it this week, or accept that your site is vulnerable until they do. There is no third option.
What to keep in your own hands
Don't assume your hosting provider patched your site. Verify. Log in and check the PHP version yourself, or have someone you trust check it for you. If you run multiple websites, check every single one. A site you launched three years ago and forgot about is still a door someone can walk through.
If you're the one who gets the panicked message at 9 p.m. that the site is down after an update, that's why you test updates on a staging site first. But in this case, the risk of not patching is worse than the risk of something breaking. Patch first, fix problems second. And this: if you're paying someone to manage your website and they didn't tell you about this patch by October 22, ask them why. You're paying them to know.