PHP2Shell by Broadcastwell
PHP2Shell: what AI engines say, and who has published
CVE-2026-109618 and CVE-2026-109619
PHP2Shell is the name researchers gave two critical PHP flaws, CVE-2026-109618 and CVE-2026-109619, fixed by the PHP project on 21 October 2026. Security vendors and hosts publish the patches. We publish what ChatGPT, Claude, Perplexity, Google AI Overviews and Google AI Mode tell site owners about PHP2Shell, what they answer when a customer asks whether a company is affected, and which companies have published a statement. Every answer is captured verbatim with its date and sources, and every row of the index links to the company's own words.
Free statement templateOur own PHP2Shell statementDownload the data (CC BY 4.0)
The AI Answer Watch
Are the engines giving site owners the right answers?
The dated captures record how the five engines answered the five questions that matter most to safety: how to fix PHP2Shell, which PHP version fixes it, whether a WordPress update fixes it, whether PHP 7.4 is patched, and whether PHP must be restarted after patching. Each answer is graded on checks anyone can verify against PHP's advisory: a correct fixed version named, a wrong version given, the WordPress-update error, the restart mentioned, the 9.2 severity stated. The scheduled watch is retired.
Capture date: 2026-10-23 UTC. These are 25 recorded answers, five per engine. "Safe answers" give no wrong fixed version, do not say that a WordPress update fixes it and state no wrong severity score; on the two version questions they also name a correct fixed version. The scheduled watch is retired.
| Engine | Safe answers | 95% Wilson interval |
|---|---|---|
| ChatGPT | 5 of 5 | 56.6% to 100.0% |
| Claude | 5 of 5 | 56.6% to 100.0% |
| Perplexity | 5 of 5 | 56.6% to 100.0% |
| Google AI Overviews | 5 of 5 | 56.6% to 100.0% |
| Google AI Mode | 4 of 5 | 37.6% to 96.4% |
These intervals describe the five answers observed per engine, not future answers. Read every answer, excerpt and capture time.
The Statement Index
Who has published a PHP2Shell statement
The reference the engines can cite when someone asks whether a company has patched. A company is "patched" only when its own statement says the fix is deployed, "mitigation only" when it reports firewall or configuration measures and no patched build, "not affected" only when the company itself says so, and "no public statement located" when we found nothing at the places we checked, printed with that date and those places. A news report never upgrades a row.
406 companies indexed: 286 Absence Index vendors, 60 web hosts and platforms, and 60 products that bundle PHP. Last source refresh: 2026-10-24T11:39:25Z.
Source review on 24 October 2026 completed for 92 of 406 company records. The other 314 records retain their earlier last checked dates because their source access or content verification did not finish on 24 October 2026. This is a partial refresh. GreenGeeks has a newly confirmed primary statement. Updated notices and scope corrections are recorded on individual company pages. Only company primary sources can establish a status.
| Status | Companies |
|---|---|
| patched | 43 of 406 |
| no public statement located | 307 of 406 |
| mitigation only | 10 of 406 |
| customer must update | 13 of 406 |
| not affected | 11 of 406 |
| patching | 10 of 406 |
| patched partly | 12 of 406 |
These are counts of the 406 listed records, not estimates for other companies. A missing statement does not establish technical exposure. Read each dated company record.
The study
What AI engines tell site owners about PHP2Shell
We asked ten site-owner questions on ChatGPT, Claude, Perplexity, Google AI Overviews and Google AI Mode, three runs each, on 23 October 2026: 150 planned cells, 148 eligible answers and two exclusions. Of the eligible answers, 23 of 148 (15.5%) were marked potentially misleading under the reviewed rubric, two of 148 (1.4%) named a wrong fixed version and two of 148 (1.4%) made the WordPress update error. The last two flags describe the same two answers and must not be added.
Reviewed and analysed by the Broadcastwell team. The work was reviewed, analysed and worked on by the Broadcastwell team. All grades are final and were approved unchanged. This is a dated descriptive snapshot, not a statistical ranking. Public answer wording is verbatim except for marked removals of attack mechanics in nine answer rows.
Read the studyDOI: 10.5281/zenodo.23586713Final grades and captured answers, CC BY 4.0
Free statement template
The statement format the engines quote
A free template built from the clearest published statements: the company name and PHP2Shell in the headline, the date and time zone, every product with its status, the fixed version deployed or the reason the company is not affected, whether workers were restarted, any temporary measures, the plan for older installations, what customers need to do, where updates will be posted, a contact and an update log. Publish it on your own domain, then submit it to the index.
Check what AI says about your company
Check what AI says about your company
Enter your company name and website. The free PHP2Shell check asks Claude one question once: whether your company is affected and has patched, with a source. Read the dated answer and its cited URLs beside your company's published Statement Index record. No email needed.
The answer and the statement record are separate observations on the dates shown. No public statement located is not proof that a company is affected. This is not a security assessment. For patching, follow PHP's advisory and your host.
Answer Repair
Put the approved facts on your page.
Publish or update your statement. Statement submission is free.
If you need a completed change, Answer Repair is $490 for one agreed buyer question and one source-backed page or fix. We work from sufficient approved facts and a named approver. This does not establish whether your runtime is affected.
Choose Live or Handoff before payment. We confirm Ready within 60 minutes during business hours. If anything is missing, a member of our team contacts you directly and finishes it with you. The deadline is 48 elapsed hours after recorded Ready. No fresh 150-answer panel or future engine result is included.
If we miss the deliverable or deadline, we initiate a full $490 refund within five business days. You keep the work. You may also request a full refund within 30 days of delivery.
Fix one answer, $490Agency Audit, $490Current scopes and pricesDelivery and refund terms
The facts we grade against
The facts we grade against
- The flaws. CVE-2026-109618 and CVE-2026-109619, each rated CVSS v4.0 9.2 by the PHP project. The PHP project does not use the name PHP2Shell; the name comes from the researchers. PHP advisory for CVE-2026-109618, 21 October 2026; PHP advisory for CVE-2026-109619, 21 October 2026.
- The fix. PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, released 21 October 2026. PHP's release notes: "There are no complete mitigations, updating is the only safe choice." PHP security advisory, 21 October 2026.
- Reported by. The PHP Foundation credits reports from Calif, OpenAI and Wiz. PHP Foundation, 21 October 2026.
- First reported attempt. Amazon Threat Intelligence reported an exploitation attempt dated 17 October 2026 in MadPot telemetry. Its report does not establish that the attempt succeeded against a real-world system. AWS report, 21 October 2026, updated 22 October 2026.
- Older branches. PHP's advisory: PHP 8.1 and older no longer receive updates from the PHP project; some distributions and long-term-support vendors provide backported fixes; the PHP security team published minimal source backports for PHP 7.4, 8.0 and 8.1.
- WordPress. WordPress.org, 21 October 2026: no WordPress update is required or planned for these issues; check with your web host.
Sources: PHP security advisory, 21 October 2026, UK NCSC alert, 21 October 2026, CERT-EU Security Advisory 2026-018, 21 October 2026, WordPress.org, 21 October 2026.
This page reports published statements and AI answers. For patching, follow PHP's advisory and your host. Last updated 23 October 2026.
Questions about PHP2Shell and this page
Questions about PHP2Shell and this page
What is PHP2Shell?
PHP2Shell is the name used for two PHP flaws, CVE-2026-109618 and CVE-2026-109619. PHP's advisories rate each CVSS v4.0 9.2. The PHP project released fixes in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 on 21 October 2026. Follow PHP's advisory and the company responsible for your PHP runtime.
How do I know if a company has published a statement about PHP2Shell?
Find the company in the PHP2Shell Statement Index and open the linked statement. Each record prints the company's published status, the statement date as printed and the source, or a dated no public statement located line with the places checked. The absence of a located statement does not determine a company's technical status.
What do AI engines say about PHP2Shell?
The PHP2Shell AI Answer Watch publishes dated answers from ChatGPT, Claude, Perplexity, Google AI Overviews and Google AI Mode. It shows the question, the captured excerpt and time, and checks against the PHP project's fixed releases. Read the dated observations rather than assuming that an engine will give the same answer to a later question.
Which PHP versions fix PHP2Shell?
PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, released by the PHP project on 21 October 2026. PHP's advisory says PHP 8.1 and older no longer receive updates from the PHP project and that some distributions and long-term-support vendors provide backported fixes, so contact your vendor or upgrade to a supported version.
Is WordPress affected by PHP2Shell?
WordPress.org wrote on 21 October 2026 that no WordPress update is required or planned for these issues. PHP2Shell is a flaw in the PHP runtime, so a WordPress site's status depends on the PHP build its host provides. Check the host's own statement and PHP's advisory; a WordPress version alone does not establish whether that site's PHP runtime has been fixed.
Is there a configuration workaround?
PHP's release notes say there are no complete mitigations and that updating is the only safe choice. PHP's advisory lists temporary settings that reduce exposure to specific attack paths but, in PHP's words, do not make an installation safe. We quote the advisory and add nothing to it.
How do we add or correct a statement in the index?
Publish the statement on your own domain or a verified official account, then submit the link on the index. We list a statement only after opening it on your own domain, and we reply from index@broadcastwell.com. Corrections to our rows follow the published dispute policy.
One buyer question. One completed repair.
We build one source-backed page or fix for $490. Choose Live or Handoff before payment. We confirm Ready within 60 minutes during business hours. If anything is missing, a member of our team contacts you directly and finishes it with you. The deadline is 48 elapsed hours after recorded Ready.
If we miss the deliverable or deadline, we initiate a full $490 refund within five business days. You keep the work. You may also request a full refund within 30 days of delivery.
Fix one answer, $490 once