Two critical PHP vulnerabilities disclosed on October 21, 2026, have prompted urgent security updates. Tracked as CVE-2026-109618 and CVE-2026-109619, the flaws can allow unauthenticated remote code execution in affected PHP installations that serve web requests. If your website runs PHP, identify the actual server-side runtime and apply the security update for your platform. Running a checker alone does not secure a server.

OpenAI has published a lightweight PHP Version Checker for the PHP2Shell vulnerabilities. It can help identify potentially vulnerable PHP versions, but it does not exploit a server, install a patch, or independently prove that the fix is active.

What is PHP2Shell?

PHP2Shell is the name used for two critical vulnerabilities in the PHP runtime. The PHP project says the vulnerabilities can affect PHP installations serving web requests, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. The official advisory rates both vulnerabilities as critical and recommends updating.

The upstream fixed releases listed by PHP are:

  • PHP 8.5.12
  • PHP 8.4.27
  • PHP 8.3.36
  • PHP 8.2.35

PHP 8.1 and older branches are end-of-life and do not receive normal upstream security updates. Operating-system vendors may provide their own security packages or backported fixes, so confirm the status of your exact distribution and package rather than relying on the version number alone.

Read the official PHP security advisory and PHP’s security release announcement.

How to use OpenAI’s PHP Version Checker

The official source code and instructions are available in the OpenAI PHP2Shell checker repository. It documents two Codex skills: one for a server you can access and another for a website URL.

Option 1: Check a public website URL

Install the skills through Codex by following the repository’s instructions, then use the URL skill:

$phpcheck-url check https://example.com

You can also run the checker directly with Node.js from the downloaded project directory:

node phpcheck.js "https://example.com"

Replace the example domain with a website you own or are authorized to assess. The tool checks version information exposed in HTTP response headers. If a site hides those headers, it may return an inconclusive result.

Option 2: Check the PHP runtime on a server

If you administer the server, the standard command is:

php -v

This command reports the command-line PHP binary, which may differ from the runtime serving the website. Check the PHP-FPM pool, Apache module, container image, LiteSpeed configuration or hosting control panel that actually runs the web application.

The checker also supports the local CLI check:

node phpcheck.js --local

Follow the official repository’s instructions for installation and use. Review commands before running them, and do not give an AI coding agent production credentials or permissions it does not need.

What do OK, VULNERABLE and UNKNOWN mean?

The checker documents these outcomes:

  • OK: The detected stable PHP version is above the tool’s embedded cutoff for a listed branch. This is a version comparison, not independent proof that the security fix is installed.
  • VULNERABLE: The detected version is at or below the tool’s cutoff for that branch. Confirm the applicable vendor advisory and update promptly.
  • UNKNOWN: The tool could not determine a supported version, did not receive usable version information, or encountered an unrecognized version. This does not mean the server is safe.

The checker reads headers such as X-Powered-By and Server, or the local php -v output. Headers can be hidden or changed. Linux distributions may also backport fixes without changing the upstream version string. Compare the result with the official advisory and your vendor’s package information.

The tool’s own limitations section explicitly says that it does not independently verify a security fix. Treat it as a triage aid, not a certification that a server is secure.

How to patch a PHP website safely

  1. Inventory every PHP runtime. Include production and staging websites, containers, workers and other internet-facing services.
  2. Identify the exact platform and package. Record the PHP branch, full package revision, operating system and hosting provider. Do not assume the command-line version matches the web runtime.
  3. Apply the correct vendor security update. Use the patched upstream release or a vendor-confirmed backported package. On managed hosting, ask the provider to confirm that the runtime serving your site has been updated.
  4. Restart or reload services as instructed. Ensure the running workers actually load the patched build; follow your operating system or hosting provider’s process.
  5. Verify after the update. Check the active web-serving runtime and package status, then test important site functions. Review logs for suspicious activity if you have appropriate monitoring.
  6. Escalate unresolved exposure. If you cannot confirm that the patch is active, contact your hosting provider or security team. Follow incident-response procedures if compromise is suspected.

Ubuntu has published platform-specific guidance explaining that it provides fixes for supported Ubuntu releases: Ubuntu’s PHP2Shell security update. NHS England also summarizes affected versions and remediation guidance in its PHP2Shell security alert.

Does the checker fix PHP2Shell?

No. The checker compares a detected version with embedded thresholds; it does not install updates, prove that a web process restarted, or determine whether an attacker previously accessed a system. PHP’s advisory says there are no complete workarounds and that updating is the safe remediation. Do not rely on disabling an unrelated configuration feature as a substitute for patching.

WordPress site owners should remember that updating WordPress core, themes or plugins does not necessarily update the PHP runtime supplied by the host. For more context about AI infrastructure, read our related article: Microsoft Maia 300 Explained: What Its AI Chip Means for Copilot and Azure. You can find additional practical AI guides on the Articles About AI homepage.

Frequently asked questions

Is PHP2Shell only a WordPress problem?

No. PHP is a server-side runtime used by many web applications. The relevant question is whether the affected PHP runtime serves web requests, not which content management system the site uses.

Does an OK result guarantee that my server is secure?

No. It means the detected version passed the checker’s embedded version comparison. Confirm the full package revision and security status with PHP or your vendor, and verify the runtime that serves web requests.

What should I do if the result is UNKNOWN?

Treat it as inconclusive. Check the active runtime through your server or hosting panel, ask the provider to confirm the patched package, and compare that information with the official advisory.

Can Codex patch my production server automatically?

Do not assume Codex has access to your server or has applied a fix. Use the documented checker workflow, review commands before execution, and follow your normal backup, approval and change-control procedures before modifying production systems.

Sources and further reading

Security note: Check the latest official PHP and platform-vendor advisories before changing a production server. Version checks alone cannot prove that a server is secure.