New — onFlow: your most critical process, automated with AILearn more
Cybersecurity

Being up to date isn't enough: what the PHP flaw left behind

  • October 23, 2026
  • By Germán Middi
Being up to date isn't enough: what the PHP flaw left behind

PHP2Shell, AI that finds flaws faster, and why today you need to stay alert as well as update

On Tuesday the details of two critical flaws in the PHP core, known as PHP2Shell, were published. They allow code to be run on a server without a username or password. They affect almost every version in use, from 5.4 to 8.5, in a language behind about 70% of websites whose technology is known.

The patch came out the same day. But there were exploitation attempts before it was published, and in the following hours they multiplied. Several European governments took sites offline while they updated, and the US security agency recommended shutting down those that couldn't be updated straight away.

AI changed the timing

The two flaws were found independently by two research teams, and both used AI models to look for them. A PHP developer had already spotted the underlying bug in a 2024 audit, but it was never fixed.

That shows where things are heading: AI makes finding flaws faster, and that applies both to those who look for them to fix them and to those who look for them to attack. The time between a flaw becoming known and it being exploited has gone from weeks to hours.

Updating isn't enough if nobody is watching

Many companies have a policy of updating "every now and then". With flaws like this, that leaves a window of days or weeks open. You also need:

  • To know which version each system runs. Including the ones in containers or on servers nobody has touched in years.
  • Someone following security alerts for what the company uses, and able to act the same day.
  • Not to stay on unsupported versions. For PHP versions that no longer have official support, the fix was released only as source code, with no ready-to-install version. Anyone on them has to sort it out by hand or migrate.
  • A plan for when you can't update right away: web application firewall rules, temporarily taking a service off the internet or limiting who can reach it.

What to do this week

If your systems use PHP, check each one's version and update to a patched release: 8.2.35, 8.3.36, 8.4.27 or 8.5.12, or the fixed version your distribution publishes. Also review your server logs from 17 October onwards.

Do you know which version of PHP runs on each of your company's systems, and who is watching the alerts? If not, get in touch and we'll review it together.

Germán Middi
Written byGermán MiddiFounder at onMedia — Software engineer, automation & applied AI.

I build digital systems that help businesses run better. From Argentina to Australia, I work with companies turning complex operations into scalable platforms. 🚀 Laravel • Vue • AI workflows • Digital transformation Let’s connect if you’re building something meaningful.

You Might Also Like

Would you like to share your thoughts?

Your email address will not be published. Required fields are marked *