Small business cyber safety

WordPress and the Critical PHP Vulnerabilities: What Site Owners Should Check

Two critical flaws in PHP can let an attacker run code on an affected web server without signing in. They are not WordPress flaws, but WordPress depends on PHP, so every site owner should confirm that the server—not only WordPress itself—has been patched.

PHP is the software underneath WordPress that processes requests and builds pages. Think of WordPress as the shopfront and PHP as part of the machinery behind the wall. Updating the shopfront does not automatically repair that machinery.

The flaws, identified as CVE-2026-109618 and CVE-2026-109619, affect PHP installations serving web requests. They can allow remote code execution: in plain terms, an attacker may be able to make the server run their instructions without first logging in. PHP and the US Cybersecurity and Infrastructure Security Agency have urged organisations to patch immediately. [1] [3]

The short version

Do not stop after checking that WordPress, plugins and themes are current. Open WordPress Site Health, find the PHP version, then ask your host to confirm in writing that the server has the fixes for both CVEs. If the host cannot confirm this promptly, escalate it. Updating PHP is the complete fix; a firewall or configuration change is not a substitute. [1] [2]

1. Find the PHP version your site is using

  1. Sign in to the WordPress dashboard.
  2. Open Tools > Site Health.
  3. Select Info, then open Server.
  4. Record the PHP version shown there.

Your hosting control panel may also show a PHP version, but check the WordPress Site Health value as well. A hosting account can contain several sites using different PHP settings. WordPress documents this same Site Health path in its security notice. [2]

2. Compare it with a fixed release

The PHP project released these fixed versions on 21 October 2026:

  • PHP 8.5: update to 8.5.12 or later
  • PHP 8.4: update to 8.4.27 or later
  • PHP 8.3: update to 8.3.36 or later
  • PHP 8.2: update to 8.2.35 or later

PHP 8.1 and older no longer receive normal security releases from the PHP project. Some operating-system or long-term-support vendors backport security fixes without changing the main PHP version number. If your host says an older version is safe, ask them to identify the vendor package and confirm that it includes fixes for both CVE numbers. Do not assume that an unfamiliar version number is patched—or unpatched—without that evidence. [1]

3. Ask the hosting provider for a clear answer

Most small-business WordPress sites run on managed or shared hosting, so the host—not the site owner—controls the server package. Send a specific question:

Can you confirm that the PHP installation serving my website has been patched for CVE-2026-109618 and CVE-2026-109619? Please tell me the PHP version or vendor package now running, when it was applied, and whether all PHP workers were restarted.

“We are monitoring the issue” is not confirmation. Neither is “your WordPress is up to date”. Ask for the installed fixed version or the vendor’s backport advisory.

If the site cannot be patched immediately

PHP says only an update is a complete solution. A web application firewall may reduce some exposure, but it does not make an affected installation safe. CISA advises organisations that cannot update immediately—particularly those on PHP 8.1 or earlier—to take PHP-based systems offline until patched or updated. [1] [3]

For a business website, discuss a temporary maintenance page, static copy or other safe fallback with the host. Do not make low-level PHP configuration changes from an online checklist unless you administer the server and understand the operational consequences.

4. Prepare before changing PHP

  • Take a fresh backup of site files and the database, and know how it would be restored.
  • Update WordPress, plugins and themes from trusted sources. This does not fix the PHP flaws, but it reduces compatibility problems and closes unrelated weaknesses.
  • Use a staging site if available, especially for an older or heavily customised site.
  • Record important functions to test: contact forms, checkout, member login, bookings, search, email delivery and scheduled jobs.
  • Choose a supported PHP branch. Moving from an obsolete branch to a current one is safer than relying indefinitely on an emergency backport.

5. Verify the result after the host updates PHP

  1. Return to Tools > Site Health > Info > Server and record the new version.
  2. Confirm that the host restarted the PHP workers or service so old processes are not still running.
  3. Test the public site and the important functions on your list.
  4. Check Site Health, hosting logs and monitoring for new errors.
  5. Keep the host’s confirmation with the date, site name and CVE numbers. This gives you evidence rather than an assumption.

6. Check for signs that the site may already have been affected

CISA added both vulnerabilities to its Known Exploited Vulnerabilities catalogue on 26 October 2026. Patching stops the vulnerable path, but it does not remove an attacker who may already have gained access. [3]

Ask the host or security provider to review activity from before the patch for unexpected administrator accounts, changed site files, unknown scheduled tasks, unusual outbound connections, and PHP worker processes launching command shells or downloading tools. If anything suspicious appears, preserve logs and backups, isolate the site where practical, reset relevant credentials from a clean device, and get incident-response help rather than simply reinstalling one plugin.

Questions to ask your web developer or host

  1. Which PHP version and package is serving this exact site?
  2. Does it contain fixes for both CVE-2026-109618 and CVE-2026-109619?
  3. When was the patch installed, and were all PHP workers restarted?
  4. If the version number is older, which vendor advisory proves that the fixes were backported?
  5. Was the site exposed before patching, and what logs have been reviewed for suspicious activity?
  6. What was tested after the update, and is there a verified recovery backup?

What this is—and is not

This is a PHP server problem, not a newly discovered WordPress-core flaw. WordPress says no WordPress update is required or planned specifically for these issues. Keeping WordPress and its extensions current still matters, but it cannot replace the PHP security update. [2]

Sources and further reading

Frequently asked questions

Will updating WordPress fix these vulnerabilities?

No. The flaws are in PHP, which runs underneath WordPress. The server’s PHP installation must be patched.

Is a security plugin or web application firewall enough?

No. It may reduce some exposure, but PHP says updating is the only complete solution.

What if my host uses PHP 8.1 or older?

Ask whether a Linux distribution or long-term-support vendor has supplied a backported package fixing both CVEs. If the host cannot prove that, move the site to a fixed, supported PHP version or take it offline until it can be made safe.

Related articles

Browse all cyber safety articles