Menu

We Don't Write PHP. PHP2Shell Still Made Us Audit Everything: A Runtime-Patching Playbook for Polyglot Teams
📰

We Don't Write PHP. PHP2Shell Still Made Us Audit Everything: A Runtime-Patching Playbook for Polyglot Teams

DEV Community: php·Lycore Development·14 days ago
#gIvHdzL9
#devto#dev#runtime#version#every
Reading 0:00
15s threshold

Our team mostly writes Django, React and Flutter, so when the PHP2Shell advisories came out last week, the first reaction in our chat was "not our problem."

That turned out to be the wrong question. The useful question isn't "do we write PHP?" It's "do we run PHP, anywhere, for anyone?" Answering that honestly sent us through an audit of every runtime we touch, not only PHP.

This post is the playbook that came out of it. It isn't about PHP being bad. Every mature runtime has had critical bugs, and the PHP project shipped a coordinated fix across four supported branches. It's about how a polyglot team makes sure a runtime-level fix actually lands everywhere it needs to.

PHP2Shell is also only one part of a rough month that security researchers have started calling "Black October". In the same weeks, at least nine AI developer platforms disclosed breaches in which attackers went after stored environment variables and API keys. I wrote that up separately in Black October: 9 AI Dev Platforms Were Breached.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.