[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fS5kaSURfC4m5B4QjGO3pz-2SwyWPfEhbFajlqeCH6dw":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"framework_notes":17,"status":23,"created_at":24,"published_at":25,"article":26,"tags":30,"podcasts":43,"controls":50},"70ce5e58-21cb-484a-828e-c34b4d6a0c11","critical-php-vulnerabilities-demand-immediate-patching-to-prevent-remote-code-execution","993daabe-a6d7-48ff-bd02-2073ce7f6d96","Critical PHP Vulnerabilities Demand Immediate Patching to Prevent Remote Code Execution","The PHP development team disclosed 17 vulnerabilities across PHP 8.2–8.5, with seven rated critical (CVSS 9.2) capable of enabling remote code execution through components like PHP-FPM, session handling, and SOAP. Because PHP underpins a vast proportion of web applications worldwide, unpatched instances represent a broad and easily exploitable attack surface. Some vulnerabilities are configuration-dependent, meaning organizations running non-default setups may be exposed without realizing it. Delayed patching in environments running critical PHP versions gives attackers a narrow but dangerous window to compromise servers, steal data, or establish persistent footholds.","**Immediate actions:**\n- Upgrade all PHP installations to the latest patched version released by the PHP development team without delay.\n- Audit your environment to identify every system running PHP 8.2–8.5, including containerized and cloud-hosted instances.\n- Review PHP-FPM, session, and SOAP configurations to identify and harden any non-default settings that expand the attack surface.\n\n**Long-term improvements:**\n- Establish a formal emergency patching policy with defined SLAs for critical (CVSS ≥ 9.0) vulnerabilities affecting internet-facing runtimes.\n- Maintain a continuously updated software inventory (SBOM) that includes runtime versions like PHP so vulnerable assets are immediately identifiable when advisories are released.\n- Adopt a web application firewall (WAF) with virtual patching capability to provide interim protection while formal patches are tested and deployed.\n\n**Detection measures:**\n- Deploy runtime application self-protection (RASP) or anomaly detection to identify exploitation attempts targeting PHP-FPM and SOAP endpoints.\n- Integrate PHP version tracking into your vulnerability scanner and configure alerting whenever a new CVE targets a detected version in your environment.",[12,13,14,15,16],"CIS Control 7: Continuous Vulnerability Management (v8)","CIS Control 2: Inventory and Control of Software Assets (v8)","NIST SP 800-53 SI-2: Flaw Remediation","NIS2 Article 21(2)(e)","OWASP A06:2021 Vulnerable and Outdated Components",{"NIS2 Article 21(2)(e)":18,"NIST SP 800-53 SI-2: Flaw Remediation":19,"OWASP A06:2021 Vulnerable and Outdated Components":20,"CIS Control 7: Continuous Vulnerability Management (v8)":21,"CIS Control 2: Inventory and Control of Software Assets (v8)":22},"This point requires security in acquisition, development, and maintenance including vulnerability handling and disclosure, which covers the obligation to track and remediate critical runtime vulnerabilities like those found in PHP.","SI-2 requires organizations to identify, report, and correct information system flaws promptly, directly addressing the need to apply the PHP security fixes within a risk-defined timeframe.","OWASP A06 specifically addresses the risk of running software components with known vulnerabilities, which is precisely the exposure created by remaining on unpatched PHP 8.2–8.5 versions.","CIS Control 7 requires organizations to continuously assess and remediate vulnerabilities; applying this to PHP runtime versions would have ensured rapid identification and patching of these 17 flaws before exploitation.","CIS Control 2 mandates maintaining an accurate inventory of all software, which is prerequisite to knowing which systems run vulnerable PHP versions and need urgent patching.","published","2026-11-20T21:21:41.949351+00:00","2026-11-20T21:21:41.9+00:00",{"id":7,"url":27,"slug":28,"title":29},"https:\u002F\u002Fwww.imperva.com\u002Fblog\u002Fphp-runtime-vulnerabilities-what-you-need-to-know\u002F","php-runtime-vulnerabilities-what-you-need-to-know-210040","PHP Runtime Vulnerabilities: What You Need To Know",[31,37],{"id":32,"name":33,"slug":34,"description":35,"color":36},"05757c8d-6b93-4194-b35d-7359e7d33b0e","Vulnerability Management","vulnerability-management","Missing scans, no risk prioritization","#fb923c",{"id":38,"name":39,"slug":40,"description":41,"color":42},"af7fce9e-1ce8-4156-93bc-09dcfbfdf29d","Patch Management","patch-management","Unpatched vulnerabilities, delayed updates","#ef4444",[44],{"id":45,"date":46,"edition":47,"title":48,"audio_url":49},"779bd2ab-1c69-4627-9085-156837e3055c","2026-11-21","morning","ThreatNoir Weekend Brief — November 21","https:\u002F\u002Fcdn.threatnoir.com\u002Fpodcasts\u002F2026-11-21\u002Fthreatnoir-morning-brief-2026-11-21.mp3",[51,54,57],{"slug":34,"name":52,"problem":53},"Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",{"slug":40,"name":55,"problem":56},"Automated patch management","Known holes get closed in days, not months.",{"slug":58,"name":59,"problem":60},"threat-intelligence","Threat intelligence","Attack campaigns reach your sector, suppliers or software before your team hears about them."]