Automate Shift
← Field Notes

October 30, 2026

Your Website Runs on PHP. Here's What the Latest Vulnerability Means for You

Illustrative trade-office scene: a coordinator and technician review a job request, with phone and calendar drawings connecting the steps.

Do I need to do anything about the new PHP security flaw?

Probably one thing: make sure whoever runs your website server has installed the PHP update released on October 21, 2026.

PHP is the programming language behind a huge share of websites, including WordPress sites. On October 21, 2026, the PHP project released fixes for two critical flaws, tracked as CVE-2026-109618 and CVE-2026-109619. Both can let an attacker run their own code on a server without logging in. Both are rated 9.2 out of 10 for severity.

You do not need to understand the bug. You need to know who is responsible for the fix.

Who patches it: you or your host?

It depends on how your site is hosted.

This is the point Jeremiah made on the Continuit Podcast: whether you or your host does the patching depends on how the site is hosted, so find out which one applies to you.

The fixed versions are PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP 8.1 and older no longer get security fixes from the PHP project. If that is you, plan an upgrade.

What to do this week

  1. Ask your host or web person two questions. "What PHP version are we on?" and "Has it been updated since October 21?"
  2. If you manage the server yourself, update PHP to a fixed version, or install your Linux provider's patched package, then restart the web service.
  3. If you cannot update right away, ask about temporary protections, such as a web application firewall rule or limiting public access to admin pages and upload forms.
  4. Write down the answer. One line in a shared note is enough: who confirmed, when, and which version.

Does this mean my website platform is unsafe?

Not by itself. The flaw is in PHP, the language underneath, not in one particular website tool. What matters is how quickly the person running your server can apply fixes. No platform is immune; every stack, old or new, has had serious flaws at some point.

The bigger lesson for small teams

Security news like this should be a routine, not a panic. Someone should own the question "who patches what?" before the next alert lands. Automate Shift builds workflows for small teams and can help you map which tools you rely on and who looks after each one.

If you want a second set of eyes on how your tools fit together, book a free Discovery Call.

Book a free Discovery Call

FAQ

What is CVE-2026-109618?

It is one of two critical PHP flaws fixed on October 21, 2026. It involves how PHP handles running out of memory, and it can allow remote code execution.

Is my WordPress site affected?

WordPress runs on PHP, so the PHP version on your server matters. Ask your host to confirm it is patched, and check your host's notices.

How do I find my PHP version?

Ask your host, or look in your hosting control panel. Many panels show it under "PHP settings" or "Software".

Sources

The ideas in this post came up on the Continuit Podcast.

The first step
costs nothing.

Book a call ↗︎Free Gap Report