Menu

PHP2Shell: The Patch Was Not the Start of the Incident
📰

PHP2Shell: The Patch Was Not the Start of the Incident

DEV Community: cybersecurity·Yano.AI Technologies Inc.·23 days ago
#ssSo35XX
Reading 0:00
15s threshold

Four days before the PHP security team published its advisory on the php2shell flaws, Amazon Threat Intelligence had already caught an exploitation attempt against its honeypot network on 17 October 2026 (Source: Amazon Threat Intelligence, 2026). In the Philippines that gap is not academic, because the National Privacy Commission requires a personal information controller to notify it within 72 hours of knowing or reasonably believing a breach has occurred (Source: National Privacy Commission, 2016). The Department of Information and Communications Technology separately requires government agencies to fix critical vulnerabilities within five business days (Source: Newsbytes.PH, 2026).

What actually broke

PHP shipped fixed versions 8.2.35, 8.3.36, 8.4.27 and 8.5.12 on 21 October 2026, covering two flaws: CVE-2026-109618, remote code execution through out-of-memory corruption, and CVE-2026-109619, remote code execution through stale global state left by an earlier request (Source: PHP, 2026).…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.