Menu

PHP2Shell: Why Laravel didn’t protect your app, and how I patched mine
📰

PHP2Shell: Why Laravel didn’t protect your app, and how I patched mine

DEV Community: laravel·yebor974·15 days ago
#4mxNwmM2
#devtolaravel#devto#dev#laravel#session
Reading 0:00
15s threshold

All my client apps running PHP 8.4 in Docker were on 8.4.27, tested and redeployed, in under four hours. Getting there was mostly a waiting game, and the slowest part had nothing to do with the code.

If you missed the last week: PHP shipped emergency fixes for two unauthenticated remote code execution bugs, nicknamed PHP2Shell. Two days later it disclosed a third, still unpatched. Here is the timeline.

Date (UTC) What happened

Oct 26 CVE-2026-109618 and CVE-2026-109619 added to the CISA Known Exploited Vulnerabilities catalog

Oct 23 PHP discloses CVE-2026-115560, no fix yet, mitigation by configuration

Oct 21, 14:00 PHP releases 8.5.12, 8.4.27, 8.3.36 and 8.2.35

Oct 21, 07:43 Cloudflare reports the first attacks, six hours before the fix

Oct 20 Details leak on social media ahead of the planned disclosure

Both October 21 bugs are rated 9.2 (CVSS v4.0) and affect every PHP version back to 5.4.…

Continue reading — create a free account

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