Key points at a glance
- The vulnerabilities CVE-2026-109618 and CVE-2026-109619 affect PHP installations that serve websites, regardless of the CMS used.
- Safe versions are 8.5.12, 8.4.27, 8.3.36 and 8.2.35, or your host's packages with the fix applied.
- After the update, the PHP processes must be restarted, otherwise the old code keeps running.
- PHP 8.1 and older no longer receive regular updates. Here, switching to a current version is the safe route.
- Ask your host or service provider today whether your server has already been updated, and have it confirmed.
What happened?
On October 20, 2026, the PHP project announced a critical security update, and the corrected versions were released a day later. Two bugs in the core of PHP were fixed, i.e. not in a plugin or an individual application, but in the programming language itself, on which a large part of the web runs.
Put simply, these are errors in memory handling. With CVE-2026-109618, PHP can leave internal data only half built when memory runs low and then process it anyway. With CVE-2026-109619, data from one request remains in memory and can be used by the next request to the same process. Under certain conditions, both errors can be exploited so that attackers execute their own code on the server. Security researchers rate both vulnerabilities as critical, with 9.2 out of 10 points (CVSS 4.0).
Particularly critical: according to the researchers, in the worst case a single request without login is enough, and the attack takes effect before your website's code is even executed. It was also shown that content can be read from memory, including passwords, credentials and keys. According to its own information, Amazon registered a first attack attempt as early as October 17, i.e. before publication. Authorities such as the UK's NCSC and the US agency CISA have issued urgent warnings, and in Germany the BSI is urging immediate updates.
Is my website affected?
Probably yes, as long as your server has not yet been updated. All PHP installations that respond to web requests are affected, whether via PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP or LiteSpeed. According to the PHP project and security researchers, it doesn't matter which CMS or shop runs on it.
Even if your website doesn't use PHP, it's worth checking the rest of your technology: PHP is found in many products, for example in the admin interfaces of firewalls, routers, hosting panels or industry software. Several manufacturers are currently checking their products; some have already confirmed that they are affected.
- Your website runs on WordPress, TYPO3, Contao, Joomla, Drupal, Shopware, WooCommerce, Magento or another PHP system
- You operate customer portals, applicant management, configurators or internal tools based on PHP
- Older projects or test environments are running that nobody actively looks after anymore
- Devices or software in your company have a web interface whose manufacturer uses PHP
These PHP versions close the vulnerabilities
The PHP project has released corrected versions for all version branches that are still supported. For the older branches 7.4, 8.0 and 8.1, there are only source code fixes that hosts or Linux distributions have to build in themselves.
Important: many hosts and Linux distributions apply the fix to their own packages while keeping the old version number. A lower number then doesn't automatically mean your server is unprotected. So don't rely on the version display alone, but have your host confirm that the fix for PHP2Shell has been applied.
| PHP 8.5 | from 8.5.12 |
|---|---|
| PHP 8.4 | from 8.4.27 |
| PHP 8.3 | from 8.3.36 |
| PHP 8.2 | from 8.2.35 (support ends Dec 31, 2026) |
| PHP 8.1, 8.0, 7.4 | no official versions, only source code fixes via host or distribution |
| PHP 7.3 and older | no fix, upgrade required |
You can usually find your website's version number in your host's customer area; in WordPress under Tools, Site Health, Info, Server.
What you should arrange now
As management or marketing managers, you don't have to install the updates yourself. But you should make sure someone does, and have it confirmed. This sequence has proven effective:
- Inventory: list all websites, shops, portals and test environments running on PHP, including old campaign pages and subdomains
- Ask your host or IT service provider in writing whether PHP has been updated on all servers and the PHP processes restarted
- For your own servers: update packages, restart PHP-FPM or the web server and check that the new version is really answering requests
- For PHP 8.1 and older: plan the switch to a supported version and test the website in a test environment beforehand
- If an update isn't possible right away: have interim measures implemented or take the application offline temporarily
- After the update, have the system checked for traces of an attack: new administrator accounts, unknown files, changed content
- Renew passwords, database credentials and API keys if the server was publicly accessible before the update
If an update isn't possible right away
For the time until the update, there are measures that reduce the risk but don't eliminate it. These include disabling a specific PHP feature for displaying upload progress on the server side and limiting the size and scope of incoming requests. Many hosts have already done this as a precaution on their servers. Providers such as Cloudflare have also provided filter rules for known attack patterns.
However, all specialist agencies emphasize: only the update closes the vulnerabilities completely. The UK's NCSC even recommends taking systems offline if they can neither be updated nor protected with interim measures. For a company website, a few hours offline is usually the lesser evil compared to a compromised server.
What an attack would mean for you
Anyone who can execute code on your web server usually has access to everything stored there: website content, contact inquiries, applications, customer data from your shop or portal and the database credentials. Typical consequences are injected malware, spam or phishing pages under your domain, ranking losses on Google and warnings in the browser.
Then there is the legal side. If personal data is affected, such as inquiries via your contact form or applications, a report to the competent data protection authority may be necessary. Under Art. 33 GDPR, this generally has to be made within 72 hours of becoming aware of the breach. In addition, Art. 32 GDPR requires appropriate technical protective measures, which include installing security updates promptly.
The bigger ongoing problem: outdated PHP versions
PHP2Shell is a particularly serious case, but not an isolated one. Each PHP version only receives security updates for a limited time: two years of full support, then two years of security fixes only, each until December 31. PHP 8.1 has been without official updates since December 31, 2025, and support for PHP 8.2 ends on December 31, 2026.
Nevertheless, many websites run on versions that stopped receiving updates long ago. According to W3Techs, on October 22, 2026, 26.9 percent of PHP websites still used version 7 and 7.7 percent even version 5. Such sites remain permanently vulnerable to new security holes, because there is simply no fix for them anymore.
Switching to a current version is rarely a push of a button. Older themes, plugins or custom developments often no longer work with new PHP versions. So plan the switch with a test environment and enough lead time, and take the end of support for PHP 8.2 at the end of this year as an occasion to check now.
Don't forget plugins and extensions
Most security vulnerabilities are not in PHP itself, but in plugins, themes and extensions. For WordPress alone, the security provider Patchstack counted a total of 11,334 new vulnerabilities in 2025, 42 percent more than in the previous year. 91 percent of them affected plugins, only six the WordPress core. For 46 percent, there was no update from the manufacturer at the time of publication.
Another figure from the report shows how quickly attackers react: for heavily exploited vulnerabilities, the weighted median time to mass attacks was only five hours. Anyone who installs updates only when they get around to it is almost always too late. Less is more here: every plugin you don't need is one less attack surface.
Security as an ongoing process
A website isn't finished after going live; it needs regular maintenance like any other technical system. For SMEs, a few simple rules have proven effective that take a lot of risk out of everyday operations.
- Name a responsible person or service provider with clear responsibility for updates
- Install security updates for PHP, CMS and plugins promptly, critical vulnerabilities within hours instead of weeks
- Delete unused plugins, themes, test environments and old microsites
- Daily backups outside the web server that are regularly restored as a test
- Protect access with strong passwords and two-factor authentication
- Keep the end-of-support dates of PHP and CMS in your calendar and plan upgrades in good time
Sources
- PHP project: announcement of the security releases (php.net, October 2026)
- Qualys: PHP2Shell, technical details, versions and interim measures
- Help Net Security: PHP2Shell, critical PHP vulnerabilities patched
- NCSC (UK): Critical security issue affecting PHP
- CISA: Critical Vulnerabilities in PHP Require Immediate Patching
- PC Games Hardware: PHP2Shell, BSI warns of dangerous attacks
- PHP Watch: New support periods for PHP versions
- W3Techs: Usage of PHP and PHP versions
- Patchstack: State of WordPress Security in 2026
- GDPR Art. 33: Notification of breaches to the supervisory authority