igors@portfolio

PHP vulnerabilities in 2026: check your version and site

Share

An up-to-date WordPress site can still run on an older PHP release. In October 2026, PHP fixed two vulnerabilities that can, under specific conditions, let an attacker run code on the server. Start with the full PHP version, such as 8.3.35, and compare it with the fixed release for that branch. The WordPress version tells you something different. Updating within your branch is routine work for a host; moving to a newer branch takes longer, because the site has to be tested on a copy first.

PHP is a programming language used to build WordPress, Joomla and other content management systems. An interpreter installed on the server runs that code. Your host or server administrator updates it separately from the CMS.

On 21 October, CERT.LV reported temporary restrictions on access from abroad to some Latvian government services. It estimated that roughly six thousand resources in Latvia might be affected and observed automated attack attempts. Its notice did not report successful compromises. Blocking a country at the edge of a private site is no substitute for updating PHP.

A password cannot stop a request handled before login

One flaw involves an out-of-memory error while PHP is handling a request. The other involves state left behind after an earlier request. In a demonstrated Apache mod_php setup, a crafted request can lead to code execution before the site's own code starts. Other server setups need their own assessment. The attacker does not need an admin password for that path.

Think of a customer sending an order form with a file. The server reads the fields and file before handing them to the shop. If PHP fails at that earlier stage, a defence inside WordPress or another CMS may never get a chance to act.

A supported branch can still have an unpatched release

In 8.3.35, 8.3 identifies the branch and 35 identifies the release within it. PHP 8.3 still receives security fixes, but release 8.3.35 predates the October patches. For these two vulnerabilities, that branch needs 8.3.36 or a later release.

PHP branchSupport status in October 2026Security support ends
7.4Ended28 November 2022
8.0Ended26 November 2023
8.1Ended31 December 2025
8.2Security fixes only31 December 2026
8.3Security fixes only31 December 2027
8.4Active31 December 2028
8.5Active31 December 2029

After active support ends, the PHP project continues to release critical security fixes until the date in the table. After that, it no longer issues regular releases for the branch. A package vendor may maintain its own build and backport a patch without changing PHP's version number. Ask the vendor about the exact package.

Find the version your site actually runs

In WordPress, open Tools → Site Health → Info → Server. Your hosting panel may show the same number. If the panel shows only 8.3, ask your host for the final part of the version and the package they install. Ask whether that package includes the fixes for CVE-2026-109618 and CVE-2026-109619.

Choose your release below. The tool shows the branch's support status and advisories matched to that release. Open an advisory to see the affected range and the developer's report, including the conditions for the flaw. An empty list does not prove the site is secure: this catalogue covers only part of PHP's issue history.

All the numbers as a table
VulnerabilityPHP releases containing the fix
CVE-2026-109618 (out-of-memory handling) and CVE-2026-109619 (state carried between requests)8.2.35 · 8.3.36 · 8.4.27 · 8.5.12

If you run 8.2.34 or 8.3.35, ask for the patched release in your current branch first. That is a smaller change than moving the whole site to a new branch immediately. A branch that has reached end of life needs a migration plan: test the CMS, plugins and custom code on a copy of the site. An old CMS that no longer receives security fixes needs its own plan too.

If the update has to wait

Installing the fix is the priority. While you wait, your administrator can reduce the requests that reach the vulnerable parts of PHP. Put these controls ahead of the site's own code, then test real forms and uploads so legitimate enquiries still work. Steps 1, 3 and 4 are PHP settings: set them in php.ini or in your hosting panel's PHP settings, if it offers them. With PHP-FPM, some settings can also be set in the pool configuration; with Apache mod_php, in the server configuration. disable_functions works only in php.ini, and max_file_uploads only in php.ini or the Apache configuration.

  1. Turn off session upload progress if the site does not use it: session.upload_progress.enabled=0. File uploads will still work, but the progress-tracking mechanism will stop. Apply this setting in php.ini, the FPM pool or a server configuration that takes effect before request parsing. Do not rely on FPM .user.ini or on ini_set() in application code: they take effect too late. Restart PHP workers after changing the setting. This limits only one documented attack path; the update fixes both flaws.
  2. Reject multipart requests where they are unnecessary at the web server or reverse proxy. Multipart is used for file uploads, and some forms use it without files. Check which routes actually need it. Enforce access restrictions before PHP. A route named /admin is not an access check.
  3. Cap request size and complexity. post_max_size caps POST data; upload_max_filesize limits the size of each uploaded file; max_input_vars caps input fields; max_input_nesting_level caps their nesting depth; max_file_uploads caps uploaded files. Where available, max_multipart_body_parts caps form parts. A web server body limit acts earlier. Set limits against real forms: a value that is too low will also reject customers. Do not lower memory_limit blindly when one flaw concerns memory exhaustion.
  4. Disable shell functions the web application does not need, using disable_functions. Candidates include exec(), shell_exec(), system(), passthru(), popen() and proc_open(). Check image processing, document generation and backup jobs first. This restricts what injected PHP might do, but code can still read files or reach the database within its permissions.

If you cannot patch and cannot reliably restrict incoming requests, CERT-EU advises considering temporary removal from public access. Once the update is installed, restart PHP workers and test forms, uploads and checkout. Before moving between branches, back up the files and database: an older plugin or custom code may need changes to run on a newer PHP branch.

Sources

If you need help confirming your PHP build, checking site compatibility and installing the fix, get in touch.

Share
← All articles