PHP2Shell statement record · Host

Liquid Web and PHP2Shell

Status in the company's own words: patching. Statement dated Oct 22, 2026 - 10:33 EDT (latest update; first Oct 21, 2026 - 09:24 EDT).

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 checked . Last refreshed .

Submit a correction or your statement Get the badge All statements

The record

Company
Liquid Web
Domain
liquidweb.com
Group
Host
Index category
not an Index vendor
Status
patching
Statement found
yes
Statement
https://status.liquidweb.com/incidents/6bfpxwg75xgj
Statement date
Oct 22, 2026 - 10:33 EDT (latest update; first Oct 21, 2026 - 09:24 EDT)
Fixed version named
yes: PHP 8.5.12, 8.4.27, 8.3.36, 8.2.35; Plesk 18.0.81.4; cPanel vendor backports 8.1.34-5, 8.0.30-12, 7.4.33-19
Worker restart stated
no
End of life plan stated
yes
Source type
status page
Places checked
Last checked

The statement

Our Engineering teams are actively working to deploy patched PHP builds across our hosting infrastructure.

Read the statement on status.liquidweb.com, dated Oct 22, 2026 - 10:33 EDT (latest update; first Oct 21, 2026 - 09:24 EDT). Source type: status page.

Notes

Our Engineering teams are actively working to deploy patched PHP builds across our hosting infrastructure. and If you are not currently patched, please try running a package update through your control panel. quoted from https://status.liquidweb.com/incidents/6bfpxwg75xgj (title: PHP Security Vulnerability Assessment (CVE-2026-109618 & CVE-2026-109619)). No completion notice at this check. Customers on EOL PHP told to update code to a supported version and switch; Plesk list marks 8.1, 8.0, 7.4 as EOL with builds dated 21 Oct 2026.

Change log

What the five engines said

ChatGPT

match

Captured . Status named: patching. Cites a liquidweb.com page.

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

Cited: status.liquidweb.com

Claude

contradiction

Captured . Status named: patched.

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

Cited: watchtowr.com, sansec.io, www.helpnetsecurity.com

Perplexity

differs

Captured . Status named: patched.

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

Cited: pulsetic.com, www.bitdefender.com, github.com

Google AI Overviews

no status named

Captured . No status named. Cites a liquidweb.com page.

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

Cited: pulsetic.com, www.therepository.email, www.imperva.com

Google AI Mode

no status named

Captured . No status named. Cites a liquidweb.com page.

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

Cited: status.liquidweb.com, www.huntress.com, www.sophos.com

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

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.

Badge

The badge for Liquid Web reads PHP2Shell statement listed, Verified 23 October 2026, Broadcastwell, and links to this record. Badge and embed code · Badge terms.

Liquid Web's customers can ask us for the PHP2Shell Record Check: we capture what ChatGPT, Claude, Perplexity, Google AI Overviews and Google AI Mode say about Liquid Web and PHP2Shell, trace every wrong or missing statement to its source and deliver a statement page in the format the engines quote. Record Check $490 once.

About this page

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