PHP2Shell: Why the patch is no longer the finish line

Oct 23, 2026
29min

Featuring

Portrait of a man with light beard and hair tied up, wearing a knitted sweater against a dark background.
Black and white portrait of a man with short hair and a beard, wearing a light-colored shirt with small patterns, looking slightly to the right against a background of vertical dark slats.
Black and white photo of a bald man with a beard and sunglasses, smiling and facing right with blurred foliage in the background.
Share

Episode description

In this episode, Sam Dickison is joined by Kev Breen, Senior Director of CTI at Immersive, and James Harris, Senior Cyber Security Engineer, to unpack what happened when PHP2Shell went public. Kev and James spent launch day reproducing the exploit with AI agents and a test range. They share what worked, what didn't, and why most public exploits aren't landing yet.

You'll learn:

  • Why a patch release is now the start of the race for attackers
  • What an n-day exploit is, and how AI has cut the time to build one from weeks to hours
  • Why most PHP2Shell exploit attempts fail against real targets
  • What to do now: patch, isolate, log headers and POST bodies, and alert when PHP spawns a shell
  • Why security through obscurity was never a defense

Resources mentioned:

About The Resilience Room: The Resilience Room is the Immersive podcast where security leaders, practitioners, and researchers talk cyber resilience, threats, and the industry. New episodes every other Tuesday.

Published:
Oct 23, 2026