October 21Oct 21 Two critical remote code execution flaws in PHP, dubbed “PHP2Shell” (CVE-2026-109618 and CVE-2026-109619), forced governments and major organizations worldwide to take websites offline on Wednesday, October 21, 2026, as the language powers roughly 70% of the internet. The vulnerabilities, rated 9.2/10 on the CVSS scale, allow attackers to execute code on servers without authentication or a password, potentially stealing credentials, API keys, and user data.PHP2Shell comprises two critical remote code execution (RCE) vulnerabilities (CVSS 9.2) tracked as CVE-2026-109618 and CVE-2026-109619. They affect all PHP versions serving web requests across PHP-FPM, Apache mod_php, php-cgi, FrankenPHP, and LiteSpeed. The PHP project released emergency patches in versions 8.5.12, 8.4.27, 8.3.36, and 8.2.35. [1, 2]The VulnerabilitiesCVE-2026-109618: An out-of-memory (OOM) error handling flaw. If PHP runs out of memory while setting up request data, the process interrupts and treats partially initialized data as valid, leading to RCE. [1, 2]CVE-2026-109619: A stale global state flaw where request-specific internal state survives after its memory is freed. A subsequent request handled by the same worker can misuse that stale data before initialization resets it. [1, 2]Highest Risk: Setups using Apache with mod_php are considered most vulnerable, allowing unauthenticated attackers to execute arbitrary code before any application code runs. [1, 2]How to Fix & MitigateUpdate Immediately: Upgrade your PHP runtime to 8.5.12, 8.4.27, 8.3.36, or 8.2.35, or apply backported packages from your Linux distribution or long-term support (LTS) vendor. [1]Apply WAF / Edge Rules: Deploy web application firewall rules (such as those provided by Cloudflare) to block oversized POST bodies or suspicious payloads. [1, 2]Isolate Unpatched Systems: If an instance cannot be patched right away (such as end-of-life PHP branches), CISA and the NCSC advise taking the affected system offline or restricting public network access behind a VPN or firewall. [1, 2]SO NOW I HAVE TO FIGURE OUT HOW TO UPGRADE TO 8.5.12 - CWP ONLY HAS UP TO VERSION 8.5.9
October 21Oct 21 Solution Sandeep has provided us with the way to build more current versions of PHP than what CWP supports by default, using his php-manager.
October 23Oct 23 Author A THIRD remote code execution vulnerability has JUST been disclosed, only 48 HOURS after PHP released emergency patches for two critical security flaws.And this one is STILL UNPATCHED.Here's what we know:NEW RCE DISCOVERED: CVE-2026-115560 could allow attackers to remotely execute malicious code on affected PHP servers.NO PATCH AVAILABLE: Even servers updated with Wednesday's emergency security fixes aren't patched against this new vulnerability.SPECIFIC CONFIGURATIONS AT RISK: The flaw requires an unusual combination of PHP session settings and application code.DEFAULT FEATURE INVOLVED: PHP's session upload progress feature is enabled by default and is part of the vulnerable configuration.OFFICIAL MITIGATION: PHP recommends setting session.upload_progress.enabled=0 until the next release.THIRD RCE IN 48 HOURS: Two critical flaws were patched Wednesday. Now another has been disclosed before a fix is available.PHP powers nearly 70% of websites with a known server-side language.THREE remote code execution vulnerabilities disclosed in just DAYS.And now another reminder that even applying the latest security patches doesn't guarantee you're protected against every newly discovered flaw."Only a narrow setup is at risk. PHP says the problem can occur when a web application does all of the following: sets the session.serialize_handler option to php_binary or php_serialize in its configuration, then changes that option to php while running by calling ini_set(), and makes that change before it calls session_start().Session upload progress must also still be turned on. An application that never changes the serialize handler while running can leave the feature on and is not exposed through this path. PHP says this setup is unlikely in practice.The action is one line. PHP recommends setting session.upload_progress.enabled=0 until the next routine bugfix release. This is the same setting it already listed as a mitigation in the October 21 advisory for CVE-2026-109619."[link to thehackernews.com (secure)]uploadprogress : An extension to track progress of a file upload.Trun it off! (For now) : session.upload_progress.enabled=0
Create an account or sign in to comment