Critical PHP Vulnerability: What WordPress Owners Should Do

Learn what PHP2Shell means for WordPress, which PHP versions contain fixes, and how Arva SEO’s plugin supports security checks. Confirm patches with your host.

Website Hacker

A critical php vulnerability has been discovered that’s causing millions of websites open to a known vulnerabilities.

If your business website runs on WordPress, ask your hosting provider to confirm that its PHP installation has been patched for CVE-2026-109618 and CVE-2026-109619, collectively called PHP2Shell. These critical vulnerabilities can allow an attacker to run code on an affected server without logging in. Both carry a CVSS v4.0 severity score of 9.2 out of 10. Singapore’s Cyber Security Agency advisory

You can also use the Arva SEO WordPress plugin connector to review PHP version warnings and scan for signs of trouble in your WordPress files. Your host still needs to apply the PHP fix. A plugin cannot replace that server update.

What is the critical PHP vulnerability?

PHP is the language WordPress uses to run much of your website. The October 2026 security release addressed two related problems inside PHP:

  • CVE-2026-109618: an out-of-memory error can leave internal data in an unsafe state, opening a path to remote code execution. PHP security advisory
  • CVE-2026-109619: a server worker can retain references to memory from an earlier request after that memory has been freed. A later request can encounter that stale state. PHP security advisory

The PHP Foundation confirmed the security release on 21 October 2026. The flaws are in the PHP runtime, so updating WordPress files alone does not replace the vulnerable software running underneath them. PHP Foundation release explanation

Singapore’s Cyber Security Agency reported widespread exploitation attempts in its advisory updated on 23 October. That makes checking your hosting environment urgent; it does not mean every WordPress website has been compromised. CSA update

Which PHP versions contain the fixes?

The PHP advisories list these fixed releases for the two original vulnerabilities:

PHP branch First fixed release
PHP 8.2 8.2.35
PHP 8.3 8.3.36
PHP 8.4 8.4.27
PHP 8.5 8.5.12

Earlier releases within each branch need attention. Ask your host for a current patched release compatible with your website. These are the first fixes for these two CVEs, rather than a permanent list of the newest PHP versions. Affected and patched versions

PHP 8.1 and older no longer receive routine security releases from the PHP project. Some vendors supply backported fixes. Ask for confirmation that both CVEs are covered, even if the displayed version stays older. PHP update guidance

Follow-up guidance after the initial release

On 23 October, PHP recommended disabling session.upload_progress.enabled pending a later fix for an unusual configuration-dependent issue, CVE-2026-115560. Ask your administrator to assess that guidance too.

On 26 October, PHP issued Windows package rebuilds ending in -1 for a separate Brotli vulnerability, CVE-2026-111497. Windows hosts should check package builds as well as runtime versions. PHP’s October updates

How to check your WordPress website

1. Find the PHP version your website uses

In the WordPress dashboard, open Tools → Site Health → Info → Server and find the PHP version. Record the full number for your hosting support request. WordPress Site Health documentation

If you manage several websites, check each one. Keep a simple list with the domain, displayed PHP version, host’s response, update date and person responsible. Include staging sites and older subdomains that are still publicly accessible.

2. Ask your host to confirm the patch

You can send this message:

Please confirm whether the PHP runtime serving my website is patched for CVE-2026-109618 and CVE-2026-109619 (PHP2Shell). Please provide the installed package or build version, or the vendor advisory confirming backported fixes, and confirm that the updated runtime is active for web requests. Please also review PHP’s 23 October session upload progress guidance and, if this is Windows hosting, the 26 October Windows package update. If work is still needed, please give me the patching time and any compatibility checks required.

PHP’s warning covers web-facing installations including PHP-FPM, Apache mod_php and LiteSpeed. Do not assume a different web server removes the need to update. PHP security notice

3. Update promptly and test the business-critical pages

Arrange the update with your host or developer. Have a recoverable backup and a short test checklist ready. After the change, test:

  • Your homepage and main service pages.
  • Contact, booking and lead forms.
  • Checkout and payment flows, if you run a store.
  • Login, account and membership pages.
  • Scheduled jobs and integrations your business depends on.

If compatibility problems appear, ask the developer to resolve them on a patched environment. Avoid making an unpatched runtime the long-term fallback.

4. Check for suspicious changes

Patching closes a vulnerability; it does not establish whether an attacker previously changed your website. Ask your host to review relevant logs and investigate unexpected accounts, files, redirects or content changes.

If anything suggests a compromise, preserve logs and involve your host or a security specialist before deleting evidence. Record what was found, when it appeared and which systems need investigation.

How the Arva SEO WordPress plugin connector can help

Install Arva SEO – Speed Booster & Security Scanner from WordPress.org. In your dashboard, open Arva SEO → Health → Security and choose Scan now.

The local security scan works without an Arva SEO account. It can help you review:

  • PHP version warnings against the plugin’s known security-release list.
  • Changed WordPress files and WordPress.org plugin files.
  • Unexpected PHP files, including code in the uploads folder.
  • Suspicious code patterns and redirects.
  • Exposed configuration files, logs and backups.

The PHP warning is a version-based check. Your host must confirm vendor backports and the actual server patch status. An absent warning is not proof that every PHP installation or package dependency is safe.

The scan does not repair files automatically. You choose supported repairs, such as restoring an official file or quarantining unexpected PHP. A clean scan cannot prove that a site is free of compromise. Plugin features and limitations

Connecting the plugin to your Arva SEO workspace adds visibility into known vulnerabilities in installed WordPress components. Sharing security scan results is a separate administrator choice. You can read more about the WordPress security scanner and the Arva SEO WordPress connector.

Use the plugin to support ongoing checks while your host handles PHP patching and any server-level investigation.

Why this matters for SEO and your customers

For a business owner, the concern extends beyond a software version. A compromised website can send visitors to unwanted pages or display content you did not publish. Google explains that hacked sites can be used for deceptive content and that Chrome may show warnings when that content is detected. Check the Security Issues report in Google Search Console. Google’s security guidance

After the update, review your important landing pages, forms and redirects. Confirm that visitors still reach the pages and actions you intended. Security maintenance supports a trustworthy website; installing a scanner or updating PHP does not promise higher rankings.

Frequently asked questions

Does updating WordPress fix PHP2Shell?

Updating WordPress does not normally update your hosting server’s PHP runtime. Keep WordPress maintained, and separately ask your host to confirm the PHP patch.

Can the Arva SEO plugin fix the PHP vulnerability?

The plugin can flag PHP version concerns and scan WordPress files for known signs of trouble. The runtime update belongs with your hosting provider or server administrator.

My host says an older version is patched. Is that possible?

Yes. A vendor may apply security fixes without changing the version number to the upstream release shown above. Request the package version and vendor confirmation covering both CVEs.

Does a clean scan mean my website was never hacked?

No. A scan provides evidence within its coverage. Combine its results with your host’s patch confirmation and investigation of any suspicious activity.

Start by confirming the PHP patch with your host. Then use the Arva SEO WordPress plugin to make regular website security checks part of your maintenance routine.

Written by

From Arva SEO

Your first website is free.

Create an account in a minute, verify your website and run your first audit. No credit card required.