Attackers who exploited a pair of PHP flaws tracked as CVE-2026-109618 and CVE-2026-109619 went on to use agentic artificial intelligence platforms for post-exploitation, The Hacker News reports — including one incident at a European government entity where operators reached password hashes and multi-factor authentication material within two hours of initial exploitation.
The outlet, which reported the case in October, presents it as one of several observations that autonomous AI tooling is moving out of proof-of-concept demonstrations and into live intrusion chains. It attributes the agentic-AI detail to the underlying research it summarises, and the specific tooling claim should be read as source-reported rather than independently confirmed until the primary advisory is checked in full.
The two-hour window
The durable takeaway here is the timeline, not the automation behind it. In the case described, operators moved from first exploitation of the PHP2Shell vulnerabilities to credential material in roughly 120 minutes — a span covering initial access, execution and credential discovery. Any triage routine built around day-scale detection deadlines is too slow against that clock, and response rehearsals that assume attackers need days to reach credentials need revisiting.
The reported use of agentic AI sharpens the point from the other direction: post-exploitation tasks that once demanded a human operator working through an access chain may increasingly be scripted end-to-end, lowering the skill floor for whatever follows initial access. Regardless of which factor dominates in a given incident, stored credential material — password hashes, MFA material, session tokens — should be handled as an asset at rest requiring protection, not merely as something guarded at the point of interactive login.
Beyond the reporting, some defenders may also consider monitoring outbound egress from web servers to external model APIs as part of layered detection.
Hardening priorities for PHP estates
- Patch or virtual-patch promptly. Apply vendor fixes for CVE-2026-109618 and CVE-2026-109619 where applicable; where patching is constrained, bridge with WAF rules or framework-level mitigations. Public mechanical detail on both CVEs was limited at the time of reporting, so confirm exact exploit conditions and patch status against primary advisories before treating any mitigation as complete.
- Restrict execution paths. Disable shell and interpreter execution in upload directories, and enforce strict file-type and permission controls on anything writable by the web server.
- Watch the web root. Alert on unexpected file creation, modification, or suspicious process spawning originating from web-serving directories.
- Protect credential material at rest. Assume hashes and MFA material are in scope during a breach: enforce strong hashing with salt, limit privileged account exposure, and shorten token lifetimes.
A general exposure question
The reported incident involved a European government body, and nothing in the source indicates targeting of any other region. But The Hacker News also reports that the same vulnerabilities were being scanned for globally — broad, opportunistic probing of internet-exposed PHP deployments rather than a bespoke operation against a single victim. That makes the underlying flaws a general exposure question for any organisation running internet-facing PHP, including environments where legacy applications linger past their support cycle. That profile is common enough that the two-hour timeline deserves a place in local incident-response planning, irrespective of who was targeted.
This article summarises reporting first published by The Hacker News.
據 The Hacker News 報道，攻擊者在利用代號為 CVE-2026-109618 及 CVE-2026-109619 的兩個 PHP 漏洞之後，進一步使用 agentic artificial intelligence 平台進行後滲透（post-exploitation）操作，其中包括一宗涉及歐洲政府機構的事故——攻擊者在首次入侵後兩小時內即已取得 password hashes 及多因素認證（MFA）相關材料。
該媒體於十月報道此案，並將其列為數項觀察之一，顯示自主 AI 工具正逐步走出 proof-of-concept 展示階段，進入實際入侵鏈條（intrusion chain）之中。報道將 agentic AI 的細節歸因於其總結的基礎研究，在未有查閱完整原始安全通告之前，關於具體工具的說法應視為來源方所述，而非獨立證實。
兩小時時間窗
此案最值得留意的是時間線，而非背後的自動化手段。在所述案例中，攻擊者由首次利用 PHP2Shell 漏洞起，約 120 分鐘內便接觸到憑證材料——當中涵蓋初始入侵、執行及憑證發掘。任何以「按天計」的偵測限期為基礎的分類流程（triage routine），面對如此時鐘都嫌太慢；而假設攻擊者需時數日才能取得憑證的應對演習，亦有重新檢視的必要。
有關 agentic AI 使用的報道，則從另一角度強化了這一論點：以往需由人手操作員逐步串通 access chain 才能完成的後滲透任務，日後可能越來越多以 script 端到端執行，從而降低初始入侵之後任何行動的技術門檻。無論個別事故中哪個因素佔主導，儲存狀態的憑證材料——password hashes、MFA 材料、session tokens——都應視為需要保護的靜置資產（asset at rest），而不只是在互動式登入環節加以防護。
除上述報道外，防禦方亦可考慮把監察 web server 向外部 model API 的 outbound egress，納入分層偵測範圍。
PHP 環境加固優先事項
- 盡快修補或進行 virtual patching。 如適用，應套用廠商針對 CVE-2026-109618 及 CVE-2026-109619 的修補；如修補受限，可先以 WAF 規則或框架層面的緩解措施補位。截至報道時，兩個 CVE 的公開技術細節仍屬有限，因此在判定任何緩解措施已完備之前，應先對照原始安全通告，確認確切的 exploit 條件及修補狀態。
- 限制執行路徑。 在上載目錄內停用 shell 及 interpreter 執行，並對任何可由 web server 寫入的檔案實施嚴格的檔案類型及權限控制。
- 監察 web root。 對來自 web 服務目錄的異常檔案建立、修改，或可疑 process 產生發出警報。
- 保護靜置狀態的憑證材料。 應假設 hashes 及 MFA 材料在事故中屬攻擊範圍：強制使用加 salt 的強雜湊方式、限制高權限帳戶暴露，並縮短 token 有效期。
一般性暴露風險問題
是次事故涉及歐洲政府機構，來源並無顯示任何其他地區成為針對目標。但 The Hacker News 同時報道，上述漏洞正遭全球掃描——針對互聯網上暴露的 PHP 部署進行廣泛、機會式的探測，而非針對單一受害者的定向行動。這意味著，對任何運行面向互聯網 PHP 的機構而言，相關漏洞都屬一般性暴露風險，包括遺留應用（legacy application）超出支援週期仍在運行的環境。此類情況相當普遍，因此兩小時時間線值得納入本地事件應對規劃之中，不論潛在針對目標是誰。
本文總結自 The Hacker News 首次刊出的報道。