PHP2Shell Exploited in the Wild

Adel Karimi, detection and response lead at Perplexity, has determined that the PHP2Shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619) have been exploited in the wild.
Steve Povolny, Vice President of AI Strategy & Security Research at Exabeam, comments, “Every few weeks a new bug gets a catchy name, the patch ships, and the industry treats the story as finished. This one is a good reminder that it isn’t. The PHP2Shell flaws went from scanning noise to confirmed remote code execution on a honeypot within days of the October 21 patches, and that gap is where most real damage happens. Plenty of sites weren’t patched on day one. Some of those servers were probably exploited before anyone noticed, and installing the fix now does nothing about an intruder who got in last week. Patching closes the door. It doesn’t tell you who is already inside.
“I think that’s the part we keep getting wrong as an industry. We measure ourselves on patch speed, which is easy to count, and spend far less effort asking whether we’d notice a compromise that already happened. An attacker with code execution on a web server doesn’t stay there. They look for stored credentials, try a few accounts, and move to something more valuable. Each step looks fairly ordinary alone. A server making an odd outbound connection or a service account logging in from somewhere new is easy to dismiss until you see the two together. The teams that handle these events well are the ones who treat the exploit as the start of the story, and they judge their servers and accounts against what normal looks like for each of them.”
News of the PHP2Shell vulnerabilities has caused a stir in the cybersecurity world, with Ben Ronallo, Principal Cybersecurity Engineer at Black Duck, calling the flaws’ announcement “a genuine drop-everything moment.”
Looking for a reprint of this article?
From high-res PDFs to custom plaques, order your copy today!





