Originally published on Kuponaut. This article has no affiliate links and recommends no paid product. Facts are taken from the PHP project’s fix list as reported by security vendors and news outlets on 21–22 October 2026; the situation is moving, so check the sources at the end for updates.
On 21 October 2026 the PHP project released emergency fixes for two critical flaws, nicknamed PHP2Shell (CVE-2026-109618 and CVE-2026-109619). Together they can let an attacker run their own code on a web server that runs PHP, without logging in, with a single request. PHP powers around 69% of websites whose server language is known, including most WordPress, WooCommerce, Joomla, Drupal and Magento sites, so this is not only a problem for big companies: a blog, a small shop or a booking page can be affected. Exploitation attempts were seen before the fix was public. This guide explains, in plain language, who is affected, how to check your site in five minutes, what to do if you cannot update today, and how governments reacted.
What the full guide covers:
- What happened, in short
- Fixed PHP versions
- Am I affected? Find your situation
- How to check your PHP version in five minutes
- If you cannot update today
- After patching: check the four things attackers change
- How countries reacted
- What about Kuponaut?
The complete version, with the dated price tables, step-by-step details and official sources, is on Kuponaut: PHP2Shell: what the critical PHP flaw means for your website and what to do today
Top comments (0)