Skip to content

OpenAI

OpenAI ships a Codex skill that checks sites for php2shell

3 min read

Our AI analyst checked this story itself: it ran, measured and compared against the originals. What we checked

Written by an AI model from the linked sources and checked against them by a second model. How we work

All about: OpenAI models and products →
Image: blockchain.news

OpenAI’s php2shell-checker, released on October 21 as two Codex skills, compares a site’s PHP version with cutoffs for php2shell, the critical PHP flaw found under OpenAI’s Patch the Planet initiative. If your server runs Ubuntu’s patched PHP packages, it will still be reported VULNERABLE: when we ran the tool, every fixed version Ubuntu lists came back that way, because Ubuntu’s fixed packages keep the old upstream version number.

To install, ask Codex $skill-installer install both skills from https://github.com/openai/php2shell-checker, then use phpcheck-url when all you have is a URL and phpcheck-server when you have server access. Without Codex, node phpcheck.js "https://example.com" checks a site and node phpcheck.js --local checks the local CLI PHP. The answer is OK (exit 0), VULNERABLE (1) or UNKNOWN (3), with --json for scripts. PHP’s fixed releases are 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP 8.1 and older get no upstream release, only minimal source backports for 7.4, 8.0 and 8.1.

What OK and UNKNOWN mean

The tool reads only the X-Powered-By and Server headers, or php -v locally. It sends HEAD, falls back to GET only on a 405 or 501, and doesn’t follow redirects. Hidden headers give UNKNOWN, and OpenAI warns that this does not mean the site is patched. OK is only a version comparison: the tool doesn’t verify the fix, and OpenAI says to check results against the official PHP security release.

Our analysis

What we checked

On October 22 we ran the checker against a local stub server, a fake php binary and 16 live sites, and reproduced its first-day code.

How we check stories

OpenAI’s backport caveat holds, and in practice it splits by distro: it hits every supported Ubuntu release and doesn’t apply to Debian. The version table also predates PHP’s advisory, so on branches PHP no longer patches, an OK can appear where no fix exists.

  • Ubuntu’s fixed 8.3.6-0ubuntu0.24.04.13, 8.1.2-1ubuntu2.28 and 8.5.4-0ubuntu1.5 returned VULNERABLE; Debian’s 8.2.35-1~deb12u1 and 8.4.27-1~deb13u1 returned OK. One run each.
  • --local has the same blind spot: with an Ubuntu 24.04-style PHP 8.3.6 (cli) banner (our reconstruction of the format), it returned VULNERABLE whatever the package revision.
  • The cutoffs are dated October 20. A nonexistent 8.1.35 or 5.4.46 returns OK, while 8.6.0RC4, which php.net says contains the fixes, returns UNKNOWN. An outside pull request would mark all of 5.4–8.1 vulnerable, but OpenAI accepts no code contributions.
  • When OpenAI tweeted the tool at 16:35 UTC, --local reported UNKNOWN for a patched 8.3.36 because it parsed “The PHP Group” as the version. An outside user reported it at 15:28 UTC, and the fix landed 68 minutes after the tweet.
  • A HEAD answered with 403 gives UNKNOWN without trying GET, and when two headers conflict, the lower version wins.
  • All 16 PHP-ecosystem sites we tried, php.net and wordpress.org among them, returned UNKNOWN with one HEAD each.

No comments yet. Be the first.

Join the conversation

Sign in to leave a comment. It appears after moderation.