If your website runs on PHP, which includes every WordPress site, ask whoever hosts it to confirm it is on PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35 or later. The PHP project released those versions on 21 October 2026 to fix two critical flaws that can let someone with no login run code on the server. For most small business sites the fix is applied by the host, so the job is a short question rather than a technical task. Our free PHP vulnerability check reads the version your site reports in a few seconds.
This is a flaw in PHP itself, not in a plugin or a theme, so a site can be fully up to date on its own software and still be exposed. Researchers at Wiz, who worked on the disclosure, describe PHP as the language behind about 70% of websites, including WordPress, Drupal and MediaWiki.
What’s affected
Both flaws are in the core of PHP and are tracked as CVE-2026-109618 and CVE-2026-109619. The PHP security team rates them 9.2 (critical) on the CVSS 4.0 scale, and the National Vulnerability Database record carries a 9.8 on the older CVSS 3.1 scale.
CVE-2026-109618. When PHP runs out of memory while handling a web request, it abandons the request part-way. The advisory says that in some cases the request’s internal data is left half set up, and PHP’s clean-up can then act on it as if it were sound. That can allow remote code execution, meaning someone outside the site getting the server to run instructions of their choosing. See the PHP advisory and the NVD entry.
CVE-2026-109619. PHP keeps some internal state tied to the current request. The advisory describes cases where that state survives after the memory behind it has been freed, so a later request handled by the same worker process can pick up stale data before it is reset. It can also lead to remote code execution. See the PHP advisory and the NVD entry.
Versions. The PHP project lists the affected branches as PHP 8.2 before 8.2.35, 8.3 before 8.3.36, 8.4 before 8.4.27 and 8.5 before 8.5.12. PHP 8.1 and older no longer receive updates from the project, and Wiz reports that releases back to 5.4 are affected by at least one of the issues. Some hosting providers and Linux vendors backport fixes to older versions, so the answer for an older PHP is “ask your provider”, not “you are fine”.
Who is at risk. PHP’s announcement says the risk covers all PHP installations serving web requests, whether through PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP or LiteSpeed. It treats mod_php as the highest risk, because an unauthenticated exploit has been demonstrated against it, working before any of the site’s own code runs. For PHP-FPM the PHP security team says its analysis points to the same weakness, though a complete exploit has not been shown.
On exploitation: on 26 October 2026 the US Cybersecurity and Infrastructure Security Agency (CISA) added both flaws to its Known Exploited Vulnerabilities catalogue, the list of flaws it has evidence attackers are using. When we first published this page on 22 October, the sources we checked described a researchers’ exploit and no attacks on live sites. If your site is not yet on a fixed version, treat the update as urgent.
How to check in a minute
- Log in to your WordPress admin.
- Go to Tools, then Site Health, then the Info tab.
- Open the Server section. The PHP version is listed there.
If it shows a version at or above the fixed number for its branch (8.2.35, 8.3.36, 8.4.27 or 8.5.12), the code is patched. If it shows a lower number in the same branch, or 8.1 or older, send your host or agency this: “Is the PHP on our hosting patched for CVE-2026-109618 and CVE-2026-109619, and which version is it running?”
One caution. Some hosts patch PHP with their own packages and keep the old version number on the label, so a lower number is a reason to ask, not proof you are exposed. The host can tell you.
What to do if you’re on an older version
- On shared or managed hosting, the host controls PHP. Ask for the answer above in writing, and ask when the update will happen if it hasn’t yet.
- If your hosting panel lets you choose the PHP version, pick the newest supported branch your site works on. Check the site afterwards, because older themes and plugins can fail on a newer PHP.
- On a server you or your developer manage, update PHP through the operating system’s package manager or your hosting vendor’s instructions, then restart the web server or PHP-FPM so the new version is in use.
- If an update can’t happen straight away, the PHP project lists interim limits in its announcement (locking the memory limit so the site can’t change it, and capping upload sizes, are among them; our checker page lists each one with its side effects). It is clear that they reduce exposure to specific attack paths and do not make an installation safe, so only the update closes the flaw.
Take a backup before any server-level change, and look at the Users list for administrator accounts you don’t recognise. That is general good practice after any serious flaw, not something the advisory reports.
Why a flaw in PHP turns into a website problem
Most small business owners never choose a PHP version. It was set when the site was first hosted, and it only changes when someone takes responsibility for changing it. When a flaw lands in the layer underneath everything, the question that matters is who owns that layer, and on a lot of sites the honest answer is nobody.
That is a maintenance question more than a security one. A WordPress site we build or take on has its PHP version, plugins and themes reviewed on a schedule, and on a support retainer we follow advisories like this one and chase the host for the fix.
Check your site now
Run our free PHP vulnerability check. Enter your website and it shows the PHP version your site reports, the fixed version for that branch, and the questions to ask your host. PHP is one layer of several, so if you want a person to look at the rest, ask for a free mini audit and we’ll email you a score and the three issues to fix first, or tell us about your site using the form below and we’ll come back with what to check first.
Written by
Alex
CEO
I’m a software developer and CEO of Digital Royalty, helping growing teams scale their SaaS platforms without losing quality, visibility, or control. I focus on building structured, maintainable systems with clear processes, reporting, and accountability. With over a decade of experience across agency and in-house roles, I specialise in delivering long-term, scalable solutions that support complex, evolving products.