/
/
Is My Website Vulnerable to the PHP Hack?

Is My Website Vulnerable to the PHP Hack?

The PHP2Shell warning affects software running behind websites, not just WordPress plugins. Here is how to find your real PHP version, check whether it is patched and decide what to do next.

Start here

Three checks tell you where you stand.

Your website could be affected if its public-facing server is running a vulnerable build of PHP. The two PHP2Shell vulnerabilities, CVE-2026-109618 and CVE-2026-109619, allow remote code execution in affected PHP runtimes. A website does not need a vulnerable WordPress plugin for the underlying problem to exist.

But a website being exposed is not the same as a website having been hacked. Work through these checks before drawing either conclusion. If you cannot answer one, ask your hosting provider.

CHECK 01

Does the site use PHP?

WordPress, Drupal, Joomla and many custom websites run PHP on their servers. A fully static site may not, although connected services can.

CHECK 02

Has PHP been patched?

Compare the web server’s PHP build with the emergency releases or get confirmation of a security backport from your host.

CHECK 03

Was anything accessed?

Even after patching, review logs and unusual changes if the site was previously exposed. A patched version cannot prove there was no earlier breach.

A domain name or a green WordPress Site Health screen alone cannot confirm that PHP2Shell is fixed. The runtime and its security patch status matter.

Finding the evidence

How to check the PHP version your website uses

You do not need to probe your website for the vulnerability. Start with your dashboard and hosting account, then verify the result with your provider.

  1. If you use WordPress, open Site Health

    Sign in to your WordPress dashboard and go to Tools → Site Health → Info → Server. Look for PHP version. Note the full number, including the final patch digit, not simply “PHP 8.3”.

  2. Check your hosting control panel

    Look for the PHP selector, PHP settings or hosting software information in your host’s dashboard. The account may run several sites or multiple PHP versions, so confirm the version assigned to the specific website.

  3. Ask which web-serving runtime was actually updated

    A terminal command such as php -v may report a command-line installation that differs from the one handling visitors. Ask the host about the active PHP-FPM pool, Apache module or other PHP web runtime.

  4. Get the full security status, not just a version label

    Some hosts apply Linux security backports that retain an older-looking PHP version. Ask for the patched package or vendor advisory and confirmation that running web workers were restarted.

Not a WordPress website?

The same issue can affect other PHP-backed websites, including Drupal, Joomla and custom systems. If you’re unsure what runs behind your site, your developer or hosting provider should check the actual application runtime. An ordinary website visitor cannot reliably determine that from a public page.

21 Oct 2026 security releases

Which PHP versions are patched?

The PHP project released fixes for four supported branches. For standard upstream PHP installations, the version must be at least the relevant number below. Earlier patches in those branches do not contain the PHP2Shell fix.

Fixed PHP releases21 Oct 2026 · PHP Security Team
PHP 8.28.2.35or later
PHP 8.38.3.36or later
PHP 8.48.4.27or later
PHP 8.58.5.12or later

Important: These are upstream PHP release numbers. A Linux vendor may have patched an older-looking package with a backported fix. Confirm that with the vendor or host rather than assuming the package is vulnerable from its headline version alone.

VERSION BELOW THE FIX

Investigate urgently

Ask for a fixed upstream build or a verified vendor backport. Treat the site as potentially exposed until confirmed otherwise.

FIXED BUILD CONFIRMED

Lower known vulnerability risk

Check the PHP workers were restarted. Continue reviewing the site for any earlier compromise.

PHP 8.1 OR OLDER

Legacy branch

These branches no longer receive normal upstream updates. Some vendors offer backports; plan a move to a supported version.

For example, 8.3.35 is below the PHP project’s fixed release, while 8.3.36 contains the upstream fix. A package labelled 8.3.6 on an Ubuntu distribution may still be protected if its vendor has backported the security update. This is why your host’s answer matters.

PHP 8.2 is also due to leave upstream security support on 31 December 2026. Fixing PHP2Shell now does not remove the need to plan a future upgrade.

What to do today

Your next steps depend on what you found.

Put the security fix first. Cosmetic site checks, plugin scans and firewall settings come afterwards.

UNPATCHED OR UNKNOWN

Ask your host to act now

Request the PHP2Shell fix for the public website and any other PHP sites, including staging environments. If a safe patch cannot be applied promptly, discuss temporarily restricting or taking the vulnerable service offline.

PATCH APPLIED

Verify and investigate

Confirm the web-serving PHP runtime and restarted workers, take a known-good backup, and check for suspicious activity from the period before patching.

What to send your hosting provider

You can use this wording whether you have shared hosting or a managed WordPress plan:

“Please confirm whether the PHP runtime serving my website is patched for CVE-2026-109618 and CVE-2026-109619 (PHP2Shell). Which PHP release or backported package is in use, when was it applied, and have the web-serving PHP processes restarted? Please also confirm whether my staging sites are covered.”

Don’t stop at WordPress, themes and plugins. Keeping them updated remains important, but PHP2Shell is in the PHP engine. Updating an extension does not replace the server’s PHP security fix. For a non-technical explanation of the flaws, see our PHP2Shell security guide.

What about a web application firewall?

Cloudflare and other providers have deployed protections against known attack patterns. Those protections can reduce exposure but do not replace a patched PHP runtime. A WAF can also be bypassed or misconfigured, so ask the host about the underlying fix.

Exposure is not proof of a breach

How can you tell whether your website was hacked?

Discovering a vulnerable PHP version does not prove someone has used it against your website. Equally, a site looking normal is not evidence that nothing happened. After securing the server, investigate signs of unauthorised activity.

ACCOUNTS

Unrecognised administrators

Look for new admin users, unexpected password changes or access from accounts that should no longer exist.

FILES

Unexpected files or changes

Review unfamiliar server files, altered website templates, scheduled jobs and configuration changes.

LOGS

Suspicious requests

Ask your host to preserve and review access, error, firewall and authentication logs, particularly around the disclosure period.

DATA

Signals of data access

Investigate unusual exports, database activity and alerts from security monitoring. A clean-looking homepage cannot rule these out.

If there are credible signs of a breach, preserve evidence, involve your hosting provider or an incident-response professional, and review sensitive credentials and affected accounts. Do not simply delete suspicious files and assume the problem is over.

A compromised website is not the same thing as an infected home router. If your concern is the household internet connection rather than the server itself, use our separate internet and router security checklist.

Ties the Meerkat, FindCheapBroadband mascot

TIES’ TAKE · THE BOTTOM LINE

Check the actual server, not just the site.

If you own a PHP-powered website, find out which PHP build handles visitors and whether the host has applied the fix. If they cannot give you a clear answer, press for one. Then check for signs of earlier compromise. A tidy dashboard is no substitute for a properly patched server.

Practical questions

Frequently asked questions

Can I check PHP2Shell by typing my website address into an online scanner?

A public scan may find useful clues but cannot reliably confirm the PHP runtime or a vendor backported fix. Use your hosting account and ask your provider to confirm the version serving live requests.

Does WordPress Site Health prove my site is safe?

No. Site Health can show the PHP version and general configuration warnings. It cannot establish that every server-side security fix is installed or that a previously exposed website has not been compromised.

Could my site be vulnerable even if WordPress is fully updated?

Yes. WordPress, themes and plugins run on top of PHP. A PHP2Shell fix must be applied to the affected PHP runtime by your hosting provider or server administrator.

Is my site safe if Cloudflare has added protection?

Not on that basis alone. Firewall rules may block known attempts, but only a corrected PHP runtime fully addresses these vulnerabilities. Confirm the patch and restart status with your host.