Insight · Security

PHP2Shell: what store owners need to do.

Two critical PHP flaws (CVE-2026-109618 and CVE-2026-109619) let attackers run code on a server without logging in. Magento, WooCommerce and Shopware stores are affected even if their own code is clean. Here’s what to check.

Line illustration of a server

In short

What happened.

  • PHP released fixes on 21 October 2026 for two flaws known together as PHP2Shell, both rated 9.2 (critical)
  • Both allow remote code execution with no login, on almost any server that runs PHP websites
  • Attacks were seen from 17 October, before the fixes were out, and broad attempts followed
  • Proof-of-concept attacks were shown against Magento, WordPress, Drupal and other popular platforms
  • The fix is simple: update PHP and restart it

Are you affected?

Affected versions and fixes.

PHP branchFixed in
8.58.5.12
8.48.4.27
8.38.3.36
8.28.2.35
7.4 to 8.1No official release. Use your Linux vendor’s patched package
Older than 7.4No fix. Upgrade PHP

Ubuntu, Debian and Red Hat backport fixes without changing the version number. Check the package changelog for the CVE, not the version.

Sources: Tenable, Sansec, Help Net Security. Checked November 2026.

What to do

Five steps for your store.

  1. Update PHP. Install your host or Linux vendor’s patched PHP package, or the fixed PHP release above.
  2. Restart PHP. Updating doesn’t patch processes already running. Restart PHP-FPM or Apache afterwards.
  3. Check the fix is in. On Ubuntu and Debian, search the PHP package changelog for CVE-2026-109618.
  4. Look for signs of compromise. New admin users, changed PHP files, unknown cron jobs or PHP files in upload folders.
  5. Plan your next upgrade. Running PHP older than 8.2 or an unsupported Magento? This is the moment to fix it.

How we handled it

What we did on our own servers.

We patched the servers we manage on the evening of 21 October, restarted PHP and checked the logs back ten days for anything suspicious. We found only generic scanner traffic, all blocked. That’s the standard every managed Magento store should get.

FAQ

PHP2Shell, answered.

What is PHP2Shell?

The name given to two critical PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619, fixed on 21 October 2026. Both can let an attacker run code on a server without logging in.

Does PHP2Shell affect Magento?

Yes. The flaws are in PHP itself, so Magento, WooCommerce and Shopware stores are affected even when their own code is clean. Updating PHP fixes it.

Do I need to take my store offline?

Usually not, if you can patch straight away. If you can’t patch quickly, talk to your host about temporary protections or taking the server offline until it’s fixed.

My PHP version number didn’t change after updating. Is it fixed?

Possibly. Ubuntu, Debian and Red Hat backport security fixes without changing the version. Check the package changelog for the CVE number.

Next step

Not sure your store is patched?