PHP Patches Seven Critical Flaws, Including a 9.2-Rated Remote Code Execution Bug
The PHP Foundation has issued security updates covering seven flaws it describes as critical, headlined by a remote code execution vulnerability tracked as CVE-2026-115560 and scored 9.2 on the CVSS scale. Deployments running PHP should treat the patch as a priority on internet-facing systems, particularly shared-hosting environments and legacy web stacks where PHP remains the execution layer for content management systems and application frameworks.
The PHP Foundation disclosed the updates in an advisory published this week. One CVE — CVE-2026-115560 — is detailed individually: an improper input validation weakness that can lead to remote code execution and file modification. The remaining six are enumerated in the same PHP advisory, which also carries the authoritative list of identifiers, affected branches and patched version numbers. The Hacker News carried an early account of the release.
Teams planning remediation should work from that advisory rather than from second-hand summaries. The version-by-branch fix table is the operative document: it determines whether a given deployment sits on a supported branch that received a patch, or on an end-of-life branch that requires an upgrade rather than a point release.
Why this matters now
Remote code execution in PHP is not a theoretical concern. The language powers a substantial share of the world's deployed web applications, and an input validation flaw that reaches code execution can be triggered through ordinary request handling — meaning the attack surface is the application itself, not an optional component. A CVSS score of 9.2 places CVE-2026-115560 firmly in the severity band where unauthenticated, network-reachable exploitation is typically assumed unless the vendor states otherwise; the exact attack prerequisites should be confirmed against the vendor and NVD records before risk scores are finalised internally.
Where the exposure concentrates
The practical pressure sits in three places. Shared hosting providers run many customer sites against a single PHP runtime, so one unpatched interpreter exposes every tenant on that host to risk. Legacy LAMP deployments — particularly those pinned to older distributions for compatibility reasons — often cannot absorb a point release without regression testing, and end-of-life branches will not receive fixes at all. And application stacks built on WordPress, Laravel and similar frameworks inherit the underlying interpreter's exposure, meaning a framework-level patch cycle alone does not close a runtime-level RCE.
What to do
- Identify the runtime. Record the exact PHP version on every server and hosting account, including those managed by third parties.
- Check the advisory. Match each version against the official PHP security advisory to determine whether it falls in an affected branch and which patched release applies.
- Patch supported branches now. CVE-2026-115560 warrants priority treatment on internet-facing systems.
- Plan upgrades for unsupported branches. If a deployment sits on an end-of-life branch, no patch is coming; schedule a version migration instead of waiting.
- Assume exposure until proven otherwise. Where a vulnerable runtime faced public traffic before the fix, review access and application logs rather than treating the update as a complete remedy.
For the affected-versus-patched mapping, identifiers and scores, consult the PHP Foundation's security advisory directly.
PHP 修補七項嚴重漏洞,包括一項 9.2 分遠端代碼執行缺陷
PHP 基金會已發布安全更新,涵蓋七項其列為嚴重的漏洞,其中以 CVSS 9.2 分的遠端代碼執行漏洞 CVE-2026-115560 最為突出。以 PHP 運作的部署應將修補列為優先事項,尤其是對外開放的系統、共享託管環境,以及以 PHP 作為內容管理系統與應用框架執行層的傳統網頁技術組合。
PHP 基金會於本週發布的安全公告中披露了這批更新。七項漏洞中,只有 CVE-2026-115560 獲逐一說明:這是一項輸入驗證不當的弱點,可導致遠端代碼執行及檔案修改。其餘六項則在同一份 PHP 公告中列明,公告亦載有權威的漏洞編號、受影響分支及已修補版本號碼。The Hacker News 曾率先報導此次發布。
規劃修補的團隊應直接參考該公告,而非二手摘要。按版本及分支整理的修補對照表才是關鍵文件:它決定某個部署是否屬於已獲修補的受支援分支,抑或處於終止支援的分支,需要升級版本而非套用點版本更新。
為何現時重要
PHP 的遠端代碼執行並非紙上談兵。此語言支撐著全球大量已部署的網頁應用,而一個可達致代碼執行的輸入驗證弱點,可透過一般請求處理觸發——攻擊面就是應用本身,而非可選組件。CVSS 9.2 分使 CVE-2026-115560 落在通常假設可未經身份驗證、經網絡直接利用的嚴重程度區間,除非廠商另有說明;內部確定風險評分前,應先向廠商及 NVD 記錄核實確切的利用前提。
暴露風險集中在哪裡
實際壓力集中在三處。共享託管服務商以單一 PHP runtime 為多個客戶網站提供服務,因此一個未修補的 interpreter 會使該主機上所有租戶暴露於風險。傳統 LAMP 部署——尤其是為相容性而鎖定舊發行版本者——往往無法在未經回歸測試下套用點版本更新,而終止支援的分支更不會收到任何修補。此外,建基於 WordPress、Laravel 等框架的應用組合,會繼承底層 interpreter 的暴露風險,僅靠框架層面的修補週期並不能關閉 runtime 層面的 RCE。
應該怎樣做
- 確認 runtime。 記錄每部伺服器及託管帳戶的確切 PHP 版本,包括由第三方管理的部分。
- 查閱公告。 將每個版本對照官方 PHP 安全公告,判斷其是否屬於受影響分支,以及適用哪個已修補版本。
- 盡快修補受支援分支。 CVE-2026-115560 對外開放的系統應列為優先處理。
- 為不受支援的分支規劃升級。 如部署處於終止支援的分支,不會再有修補;應安排版本遷移,而非等待。
- 在證實安全前假設已受影響。 若 vulnerable runtime 在修補前曾面對公開流量,應檢視存取及應用日誌,而非視更新為完整補救。
受影響與已修補版本的對照、漏洞編號及評分,請直接查閱 PHP 基金會的安全公告。
