Skip to content
IEEE Spectrum·

🛡️PHP2Shell Bug Lets Attackers Run Code on WordPress and Drupal Servers

Your PHP servers need patching before AI finds the next one

TL;DR

A PHP2Shell vulnerability surfaced in late October, putting WordPress and Drupal sites at risk. Researchers used AI tools to turn an out-of-memory bug into remote code execution. A patch shipped before attackers got there, but the bug was reported back in 2024. Update PHP now.

A bug in PHP that most people assumed was harmless just became a way to run arbitrary code on a server. Researchers found that an out-of-memory error, normally just a crash, could be chained into remote code execution. WordPress and Drupal sites are the obvious exposure, and the researchers' AI tooling is the reason the chain got found. If you run PHP in production, this is your problem. Most WordPress and Drupal installs sit on boxes nobody has touched in months, and that's the attack surface. The researchers alerted the PHP Foundation right away, and a patch landed before any bad actors had the exploit. The catch: the underlying bug was reported as far back as 2024, which means it sat around for a long time. The patch took a team of four engineers two months to build. The original bug report dates to 2024, and the exploit chain was disclosed in late October. Nobody exploited it in the wild before the fix. Bottom line: this one got lucky, and the next one might not. Update PHP and your CMS plugins this week.

PHP2Shell Bug Lets Attackers Run Code on WordPress and Drupal Servers — IEEE Spectrum

Key Points

1

The underlying bug was reported to the PHP Foundation in 2024, then the exploit chain surfaced in late October, giving the bug roughly a year of exposure before disclosure.

Keep reading — it's free

Enter your email to keep reading — plus the best of AI & tech, daily. Free, forever.

Also get
or

Already a member? Sign in

PHPWordPressDrupalVulnerabilityAI Security

Comments

Subscribe to join the conversation...

Be the first to comment