PHP security audit and upgrade: patch the October 2026 PHP vulnerabilities and move off end-of-life PHP

On 21 October 2026 the PHP project fixed two critical flaws that let an attacker run code on a server without logging in, and five days later the US Cybersecurity and Infrastructure Security Agency listed both as exploited in the wild. If your site or application runs PHP older than 8.5.12, 8.4.27, 8.3.36 or 8.2.35, it is exposed. If it runs PHP 8.1 or older, no fix exists for that version at all.

We audit PHP code, dependencies and server settings, apply the urgent patches, and upgrade older applications to a supported version with tests, so the fix does not break the site. Our project records hold 1,300+ PHP projects, including upgrades and rescues of code we did not write.

What happened in October 2026

Facts as of 16 November 2026, from the PHP project, GitHub security advisories and the CISA Known Exploited Vulnerabilities catalogue.

PHP published two critical advisories on 21 October 2026, CVE-2026-109618 ("RCE via OOM corruption") and CVE-2026-109619 ("RCE via stale global state"). RCE means remote code execution: someone outside your business can make your server run their code. CISA added both to its Known Exploited Vulnerabilities catalogue on 26 October 2026, which means attacks have been seen.

PHP branchFixed inSecurity fixes until
8.58.5.1231 Dec 2029
8.48.4.2731 Dec 2028
8.38.3.3631 Dec 2027
8.28.2.3531 Dec 2026
8.1, 8.0, 7.x and olderNo fix: end of lifeEnded

Support dates are from php.net. PHP 8.2 receives its last security fixes until 31 December 2026; after that it joins 8.1 and older without fixes. The September, July and May 2026 releases also fixed smaller issues in FPM, OpenSSL, SOAP, Phar and the PostgreSQL extension (PHP 8 ChangeLog), so a site that skipped them is behind on more than one fix.

The applications built on PHP had their own exploited flaws in 2026

  • WordPress core: CVE-2026-87902, a path traversal leading to code execution (fixed in 7.1.2, 7.0.6, 6.9.9 and backports), and CVE-2026-119977, fixed in 7.1.4 on 28 October. Both are in the CISA catalogue.
  • Drupal core: SA-CORE-2026-004, a highly critical SQL injection (CVE-2026-9082) published 20 May 2026.
  • Adobe Commerce and Magento: APSB26-73, an unrestricted file upload (CVE-2026-48356) fixed in July and listed as exploited on 27 October.

Patching PHP itself does not fix these. The platform, its plugins and the Composer packages your code depends on need checking too.

How to check which PHP version you run

  1. Run our website version checker: it shows the PHP version your site announces publicly, if any, and whether it is out of date. Most well-set-up servers hide the version, so if the checker cannot see it, use one of the steps below.
  2. Ask your host, or look in the hosting control panel (cPanel, Plesk and most managed hosts show the PHP version per site).
  3. On a server you manage, run php -v for the command line and check the web server separately: the web and command-line versions can differ.
  4. In WordPress, Tools > Site Health > Info > Server shows the PHP version.
  5. Compare the result with the table above. Anything below the "Fixed in" version needs patching now; anything on 8.1 or older needs an upgrade.

Do not leave a phpinfo() page on a live site to check: it tells attackers the same thing.

What the PHP security audit covers

You get a written report that ranks each finding by risk and effort, separates what must be fixed this week from what can wait, and says what we would change.

Version and patch status

The PHP version on every server and container, the extensions loaded, and the patches missing against the PHP, OS and web server releases.

Dependencies and platform

Composer packages checked with composer audit against published advisories, plus CMS core, plugins and themes (WordPress, Drupal, Magento, OpenCart).

Code review

The risks in the OWASP Top 10:2025: injection, broken access control, authentication failures, insecure design and supply-chain issues, starting with forms, uploads, log-in and admin areas.

Server configuration

php.ini settings from the OWASP PHP Configuration Cheat Sheet: display_errors and expose_php off, allow_url_include off, dangerous functions disabled, secure session cookies.

Uploads and files

Where users can upload files, where they are stored, whether they can be executed, and what the web server will serve from those folders.

Logging and recovery

Whether errors and log-ins are logged and someone is alerted, and whether backups exist and have been restored at least once.

From audit to a supported PHP version

  1. Patch what is urgent. Moving to the latest release of the branch you already run (for example 8.3.x to 8.3.36) is usually low risk and closes the October flaws on supported branches.
  2. Audit. Version, dependencies, code and configuration, as above, with a ranked report.
  3. Plan the upgrade. For 8.2 and older we scan the code with PHPCompatibility, apply the mechanical changes with Rector, and list what needs a developer: removed functions, changed behaviour, framework and plugin versions.
  4. Test before it goes live. The upgraded site runs on a staging copy first, with automated tests where they exist and a written test plan for the paths that earn money: log-in, checkout, forms, payments.
  5. Keep it current. PHP has a release roughly every month. A maintenance plan keeps PHP, the platform and its packages patched after the upgrade.

Our guide to PHP versions and support dates explains the upgrade path in more detail, and our PHP development page covers the wider work we do in PHP.

Frequently asked questions

Is my site at risk from the October 2026 PHP vulnerabilities?

If it runs PHP below 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or any version of PHP 8.1 or older, assume yes until it is patched or upgraded. The two flaws (CVE-2026-109618 and CVE-2026-109619) are rated critical and are listed by CISA as exploited.

My host manages PHP. Do I still need to do anything?

Check which version your host runs for your site and whether it has already applied the October releases. Many hosts let each site choose its PHP version, so an old setting can stay in place for years. Your own code, plugins and Composer packages are your responsibility either way.

Will upgrading PHP break my site?

A patch release within the same branch rarely does. A jump across major versions, such as 7.4 or 8.0 to 8.3 or later, can: removed functions and stricter types surface as errors. That is why we scan the code first, upgrade on a staging copy and test the important paths before the live switch.

What happens to PHP 8.2 after 31 December 2026?

The PHP project stops releasing security fixes for it, as it already has for 8.1 and older. Any flaw found after that date stays open on 8.2. Plan the move to 8.3 or newer now; 8.4 receives security fixes until 31 December 2028 and 8.5 until 31 December 2029.

Do you only audit code you wrote?

No. Most of the PHP we audit and upgrade was written by someone else, often years ago and without documentation. We start with read access to the code and a copy of the database, never with changes on the live server.

What does the audit cost and how long does it take?

It depends on the size of the code base, the number of sites and servers, and the platform. Tell us what you run and we come back with questions, a suggested scope and a quote.

Need a PHP site checked or upgraded?

Tell us the PHP version if you know it, the platform (custom, Laravel, WordPress, Magento or other) and where it is hosted. We come back with questions, a suggested scope and a quote.