PHP2Shell statement record · Host
Liquid Web's PHP2Shell statement is recorded as patching, with statement date printed as Latest update Oct 23, 2026 - 22:25 EDT; read the published statement.
This index reports published statements and AI answers on stated dates. It is not a security assessment. For patching, follow PHP's advisory and your host.
Submit a correction or your statement Get the badge All statements
Publish or update your statement. The statement submission is free.
See what ChatGPT, Claude, Perplexity, Google AI Overviews and Google AI Mode say about you: the $490 PHP2Shell Record Check.
We capture the dated answers, trace wrong or missing statements to their sources and deliver a statement page in the format the engines quote.
Agencies: white-label PHP2Shell Record Check, $490 per client report.
Read the statement on status.liquidweb.com, dated Latest update Oct 23, 2026 - 22:25 EDT. Source type: status page.Patch deployment is ongoing across our fleet. We appreciate your continued patience.
Patch deployment is ongoing across our fleet. We appreciate your continued patience.
The latest official update explicitly says patch deployment remains ongoing. No completion is inferred from the availability of package builds. Existing supported-version migration guidance remains in the source.
match
Liquid Web lists affected hosting services and is deploying patches, but has not confirmed that all systems are patched. As of my check on October 23, 2026, its latest official update is dated October 22, 2026, at 3:28 p.m. EDT. Affected services: Its PHP2Shell incident lists Cloud Dedicated, Cloud VPS Hosting, cPanel, InterWorx, and Plesk. This does not mean
contradiction
Based on my research, I was not able to find any specific statement, advisory, or announcement from Liquid Web regarding PHP2Shell (CVE-2026-109618 and CVE-2026-109619). There is no publicly available source — as of today, October 23, 2026 — in which Liquid Web has confirmed whether it is affected or has patched these vulnerabilities. I cannot fabricate or assume their
differs
Yes—Liquid Web was affected if its systems were running unpatched PHP, because PHP2Shell affects PHP versions dating back to 5.4. Liquid Web’s incident notice said its hosting infrastructure was under assessment and that, initially, no patches had yet been deployed to production. Liquid Web subsequently listed patched builds for its platforms, including: cPanel: PHP 8.5.12, 8.4.27, 8.3.36, 8.2.35, plus
no status named
Liquid Web is affected by the PHP2Shell remote code execution vulnerabilities (CVE-2026-109618 _BLzaaqjPIOexur8PmZGXoQ8_17 and CVE-2026-109619 ), and as of October 21–22, 2026, the company was actively rolling out emergency patches and mitigations across its hosting environments. Status & Impact Vulnerability: PHP2Shell affects web servers running PHP 5.4 and later, allowing unauthenticated remote code execution (CVSS score of 9.2). Liquid
no status named
Liquid Web is assessing and addressing the PHP2Shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619), which affect various server configurations running vulnerable PHP versions. According to their official status and engineering response: Impact Status: Liquid Web's Security and Engineering teams actively reviewed hosting environments to determine potential impact across servers running vulnerable PHP iterations. Patch/Mitigation Status: Liquid Web stated they are implementing
One card per engine, the latest capture. Every capture is in ai-answers.json. Answers are captured through the engines' APIs and Google's answer surfaces, verbatim, with cited URLs, under the Broadcastwell method v1.1; one answer per engine per question per day for the watch.
Submit a correction or your statement. We list a statement only once we have opened it on your own domain or verified official account. Disputes follow the dispute policy. Or email the statement link to index@broadcastwell.com.
The badge for Liquid Web reads PHP2Shell statement listed, Verified 24 October 2026, Broadcastwell, and links to this record. Badge and embed code · Badge terms.
Liquid Web's PHP2Shell statement is recorded as patching, with statement date printed as Latest update Oct 23, 2026 - 22:25 EDT; source: https://status.liquidweb.com/incidents/6bfpxwg75xgj.
The status records what the company published, under our statement status rules. A PHP version mentioned in a statement can be guidance for other organisations; the statement and notes explain its scope.
This index reports published statements and AI answers on stated dates. It is not a security assessment. For patching, follow PHP's advisory and your host.
Last refreshed .
PHP2Shell Statement Index · AI Answer Watch · Download the data · Submit a statement · Dispute policy