Critical · Patched Oct 21, 2026

PHP2Shell

Attackers can take over a PHP website, including WordPress, with a single request and no password. It's being exploited right now.

The risk

Customer and payment data stolen, card skimmers planted

  • Malware served to everyone who visits your site
  • Full takeover of your site with a single request, no password needed
  • Hidden admin accounts and backdoors that survive cleanup
  • Your server used to attack others or send spam
  • Site defaced or knocked offline

Who is affected

  • PHP
  • WordPress
  • WooCommerce
  • Laravel
How to fix it

Fix it yourself.

  • Find your PHP version. Run php -v or check your hosting panel.
  • Update and restart. Move to 8.5.12, 8.4.27, 8.3.36 or 8.2.35, then restart PHP.
  • Check for intruders. Review logs since October 17 for anything unusual.

CVE-2026-109618 & CVE-2026-109619 · Critical · CVSS 9.2

PHP branchVulnerableFixed in
8.5below 8.5.128.5.12
8.4below 8.4.278.4.27
8.3below 8.3.368.3.36
8.2below 8.2.358.2.35
8.1, 8.0, 7.4 and olderyesNo official release. Upgrade, or use your distribution's patched package

Both flaws are rated CVSS 9.2. All deployment types are affected: Apache mod_php (highest risk), PHP-FPM, php-cgi, FrankenPHP and LiteSpeed. The PHP project says no configuration change fully mitigates them. Found with help from AI (OpenAI's GPT-5.6 Sol and OpenAI's own team; Wiz found them independently). Exploitation attempts began October 17, 2026, four days before disclosure.

Sources: Help Net Security: PHP2Shell patched · AP / PBS NewsHour · watchTowr FAQ · Datadog Security Labs. Last updated October 26, 2026.

A client who dealt with this.

★★★★★

"A critical vulnerability hit our WordPress site and we needed answers fast. LastGap confirmed we were exposed, guided us through every step of the fix, and we had it fixed before anyone could exploit it."

Sabrina Loo
Sabrina LooCEO, Pallaris

Questions

Is my WordPress site affected by PHP2Shell?

WordPress runs on PHP, so a WordPress site is affected if its server runs an unpatched PHP version. Updating WordPress itself does not fix it; the server's PHP must be updated to 8.5.12, 8.4.27, 8.3.36, 8.2.35 or later.

Does a firewall or Cloudflare protect me?

A web application firewall blocks many attempts, but the PHP project says no configuration change fully mitigates these flaws. Patching PHP and restarting the server is the only complete fix.

What if I can't update right away?

The FBI advised taking affected websites offline until they can be updated.

Not sure if this affects you?

Check my site