Skip to content

Light version: pages open quickly, without the 3D graphics. You are seeing the light version because the 3D graphics would be slow on this device. The content is the same.

Turn on 3D

Preparing the graphics. This can take a moment on the first visit.

Henry Lõiv

Web design & development

Website Security 5 min read

Critical PHP vulnerabilities and protecting your website

Fixed versions for two critical PHP vulnerabilities, how to check PHP in WordPress, and what to ask your host. Includes guidance for older PHP installations.

Status as of 21 October 2026 at 16:36 Estonian time (UTC+3). PHP has published fixes in versions 8.2.35, 8.3.36, 8.4.27 and 8.5.12.

A WordPress website can appear to work perfectly while its server software needs an urgent security update. Two critical PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619, can allow an attacker to execute code without logging in. PHP's security team urges users to update immediately. Official PHP security notice.

As the website owner, first establish whether your hosting provider has patched the PHP installation serving your website. An update in the WordPress dashboard does not automatically update the server's PHP runtime.

Which PHP versions need updating

Both official advisories give these cutoffs for supported PHP branches. The table identifies the first fixed release in each branch; a later maintenance release in the same branch also includes these fixes.

PHP branchAffected versions in that branchFirst fixed version
8.2Earlier than 8.2.358.2.35
8.3Earlier than 8.3.368.3.36
8.4Earlier than 8.4.278.4.27
8.5Earlier than 8.5.128.5.12

These cutoffs come from PHP's advisories for CVE-2026-109618 and CVE-2026-109619. PHP's source releases are on its downloads page; check with your supplier for availability in your hosting environment or Linux package repository.

If you use PHP 8.1 or an older branch, ask your provider for a specific remediation plan. These branches are outside PHP's regular upstream support. For this incident, PHP supplied minimal source backports for 7.4, 8.0 and 8.1. That does not restore their general security support or mean those fixes have reached your server. Some distributions and long-term-support suppliers may provide patched packages. PHP security notice.

The complete package version matters. A distribution can backport a security correction into an earlier PHP version. Ask for confirmation that both CVEs are fixed in the supplier's package; the short upstream version number alone may be insufficient. Ubuntu's explanation of security updates.

What happened inside PHP

PHP runs the server-side code behind WordPress, WooCommerce and many other web applications. These two vulnerabilities concern its internal memory handling.

With CVE-2026-109618, handling an out-of-memory error can leave request data in an invalid state that cleanup later consumes. With CVE-2026-109619, a server worker can retain a reference to released memory and use it during a later request. Successful exploitation can execute code with the web worker's privileges. First advisory, second advisory.

PHP says all installations serving web requests should be treated as at risk. It considers Apache's mod_php especially exposed, with a demonstrated attack before application code executes. PHP-FPM also needs updating. Exact exploitation conditions depend on the vulnerability, configuration and application; using PHP does not establish that a website has already been compromised. PHP security notice.

How to check your WordPress PHP version

Sign in to your website's WordPress dashboard and open Tools → Site Health → Info → Server. This shows information about the PHP installation serving that website. Ask your host for assistance if necessary. WordPress Site Health documentation.

Your developer should also check separate subdomains, staging environments, background jobs and containers. The PHP version for one website or a command-line session does not verify every other environment. Record which domain or service each result describes.

What to ask your hosting provider

Send your provider the domain and ask for a concrete answer:

Has the PHP installation serving my website been patched for CVE-2026-109618 and CVE-2026-109619? Please confirm the running version or patched package identifier, when the update was applied, and that the workers serving the website are using the corrected software.

On managed hosting, the provider usually handles the PHP update. On your own virtual server or containers, the designated server administrator handles it. Your developer should then check important website functions: sign-in, contact forms, file uploads and, for a shop, the basket and order submission. The exact division of responsibility depends on your service and agreement. WordPress server administration guidance.

Before the update, confirm that you have a backup of both files and the database, and a way to restore them. Coordinate this with the responsible administrator so the urgent update and necessary checks can proceed.

Temporary measures need a server administrator

The circulating advice to disable session.upload_progress.enabled addresses only some paths through the second vulnerability. PHP's official guidance requires applying it before request parsing and restarting all workers. FPM's .user.ini or an application-level ini_set() is too late for this measure. The complete solution is patched PHP. PHP security notice.

A firewall rule or WordPress security plugin also cannot establish that both flaws have been removed. If an update is unavailable, your administrator needs to choose temporary restrictions for the specific environment. CERT-EU recommends considering restricted public access or isolation until remediation is possible. CERT-EU guidance.

What to check after the update

Confirm the running service's version, check important website functions and retain logs. Unknown users, changed files, unexpected redirects or other suspicious activity require investigation. A security patch closes the vulnerability, but changes left by an earlier intrusion may remain. WordPress guidance for a compromised website.

A normal-looking website and a clean dashboard do not establish that every environment has been patched. Ask for a verifiable result from the technical work: which service was updated, which corrected package is running and what was checked afterwards.

Written by Henry Lõiv

Keep reading

All articles⁠
  1. Best AI agents in 2026: Grok Bot vs Dots and EU availability Compare AI agents by the work they can handle and whether you can use them in Estonia or the EU. Artificial Intelligence 5 min read
  2. AI Agent, Chatbot or Automation: What Does Your Business Need? A chatbot is an interface; an agent is one way to handle the work behind it. Follow a fictional customer enquiry to choose a practical system for your business. Artificial Intelligence 8 min read
  3. Claude Code vs Codex for Frontend Development: A Practical Comparison A documentation-based comparison with a runnable frontend exercise and a blank scorecard. No measured winner is claimed. Artificial Intelligence 9 min read

Hi!

I really love the sea, yachts, sunsets and starry skies.

Through this little 3D world, I can share a small part of myself with you.

Thank you for opening this bottle and reading my letter.

Henry

Let’s talk about your project

Tell me about your project

Tell me what you’d like to build or improve. You don’t need a finished brief — we’ll work out the scope and next steps together.

01 How can I help?
02 How many pages do you need?
03 Which extras do you need? Choose all that apply
04 When does it need to be ready?
05 Project details
06 Your contact details

Enquiry received

Thank you!

Your enquiry has been received. I usually reply by email within 2 working days.