• News/
  • theregister-5305336

PHP2Shell: No login, no app code, no warning. What next?

The Register
·
Published Oct 26, 2026
·
Updated

If you run PHP anywhere in your environment, patch to PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35 now. Two critical flaws disclosed last week, CVE-2026-109618 and CVE-2026-109619 (nicknamed "PHP2Shell"), let an unauthenticated attacker run code on a server with nothing more than a crafted web request. Both carry a CVSS v4.0 score of 9.2, every earlier release is affected, and exploitation in the wild has been reported. The patch is the easy part. The hard part is finding every copy of PHP you own, because PHP rarely shows up where you expect it. This post covers what the flaws are, how far exploitation has gone, and how to get to full coverage fast. Details leaked before the planned embargo, so the PHP security team moved fast and shipped fixes within about a day of announcing them.

Both bugs live in PHP core, not in any framework or plugin, so they reach anything that runs PHP to serve web requests.

Affected server setups include PHP-FPM, mod_php, php-cgi, FrankenPHP and LiteSpeed. PHP rates mod_php as the highest risk. No login is needed: the attacker only has to reach a PHP endpoint over HTTP. Fixed versions: 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Every earlier release is affected. PHP has also published minimal source backports for 7.4, 8.0 and 8.1, but there are no official releases for those branches. Treat a backport as a stopgap and plan the upgrade. Yes, though reliable public exploits are still scarce. watchTowr reports exploitation in its honeypot network as of October 21, ...

Read full article

Affected Software

4 affected components
PHP PHP<8.2.35
PHP PHP>=8.3.0<8.3.36
PHP PHP>=8.4.0<8.4.27
PHP PHP>=8.5.0<8.5.12

Frequently Asked Questions

1

Which PHP deployments are affected by the PHP2Shell flaws?

Every PHP release earlier than 8.5.12, 8.4.27, 8.3.36, or 8.2.35 is affected. The flaws are in PHP core and can affect PHP-FPM, mod_php, php-cgi, FrankenPHP, and LiteSpeed deployments that serve PHP web requests.

2

What does an attacker need to exploit these vulnerabilities?

An attacker does not need a login or application code access. They only need to reach a PHP endpoint over HTTP and send a crafted web request to execute code on the server.

3

What should defenders do first?

Patch PHP immediately to 8.5.12, 8.4.27, 8.3.36, or 8.2.35. Organizations should also identify every PHP instance in their environment, since PHP may be present in unexpected locations.

4

Is exploitation confirmed?

The article reports exploitation in the wild. Both CVE-2026-109618 and CVE-2026-109619 have a CVSS v4.0 score of 9.2.

5

Are frameworks or plugins the source of the issue?

No. Both vulnerabilities are in PHP core rather than a framework or plugin, so they affect anything using PHP to serve web requests.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203