Two critical remote code execution vulnerabilities, CVE-2026-109618 and CVE-2026-109619, were addressed in PHP on 21 October 2026. The issues, collectively referred to as PHP2Shell, received a CVSS 4.0 score of 9.2 and permit unauthenticated attackers to execute arbitrary code on affected servers.
Patches are available in versions PHP 8.2.35, 8.3.36, 8.4.27, and 8.5.12. All earlier releases remain vulnerable, impacting popular platforms including WordPress, 1C-Bitrix, Drupal, OpenCart, Laravel, Magento, Joomla, MediaWiki, phpBB, Symfony, and WHMCS. Updating the CMS or framework alone does not resolve the problem because the flaw resides in the PHP interpreter itself.
Immediate Actions Recommended
- Identify the team or contractor responsible for server maintenance.
- Upgrade PHP to a patched release; temporary mitigations listed in the security bulletin do not replace the update.
- Restart PHP-FPM, web servers, and any queue processors to clear vulnerable code from memory.
- Run php -v and php-fpm<VERSION> -v, then archive the output together with the date, performer identity, and any contractor confirmations.
- Scan for indicators of compromise such as unexpected files, new accounts, or suspicious log entries.
Preserving these records is critical because Russian courts have previously held organizations liable for data leaks when they failed to apply known security updates, even when maintenance was outsourced. Under Federal Law No. 152-FZ, the data controller remains responsible regardless of third-party involvement.
If unauthorized access to personal data is confirmed, companies must notify Roskomnadzor within 24 hours and submit a detailed follow-up report within 72 hours. Subjects of critical information infrastructure must also alert the National Coordination Center for Computer Incidents under Federal Law No. 187-FZ.


