PHP2Shell: Exploit Attempts Surge as Patching Complexity Slows Defenses
In 48 hours following disclosure of PHP2Shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619), exploitation attempts spiraled from thousands to millions. Cloudflare tracked the acceleration: thousands pre-announcement, tens of thousands within 45 minutes of public disclosure, and millions within hours. Check Point Research documented that 10% of organizations were targeted within two days, yet patching significantly lagged—97.5% of discoverable PHP instances remained unpatched 48 hours after fixes became available. Cisco Talos estimates roughly half of all PHP systems will never receive patches.
The patching lag reflects genuine technical hurdles. Organizations struggle to inventory PHP across their entire infrastructure; the language exists not only on web servers but embedded in storage systems, physical access controls, and cameras. Most production PHP runs on legacy versions (5 or 7) where updating would require substantial application rewrites and dependency replacements. Hardware and embedded systems often depend on manufacturer firmware updates, and many legacy appliances no longer receive support.
Interim defenses exist for those unable to immediately patch. Disabling the session.upload_progress feature blocks the known exploitation path for CVE-2026-109619 without requiring a version upgrade. Organizations should take vulnerable systems offline entirely if they cannot be patched. Deployment size shapes response: small organizations can patch quickly, while large enterprises using golden-image models face added friction in rolling updates to production.
Read the full article
Continue reading at Dark Reading →This is an AI-generated summary. Read the original for the full story.