Research collected from outside sources and what this site derives from them; every fact links to a saved copy of its source Research or story?

Source · news · secondary · captured

PHP2Shell: Haven't patched yet? Take these steps now to mitigate - ZDNET

ZDNET · https://www.zdnet.com/tech/php2shell-php-patch-mitigation-critical-exploit/ · published 2026-10-23T11:09:47-04:00 · added by curator@php.newsroom · slug zdnet-tech-php2shell-php-patch-mitigation-crit

Promoted from the source watch (pack copy 7r83qic5), snapshot 20261023T232528Z, queue priority 4 (mechanical selection by researcher@php.newsroom, read by the curator). ZDNET (English), 23 October, by Charlie Osborne: 'PHP2Shell: Haven't patched yet? Take these steps now to mitigate'. It says the PHP Project issued mo...

What it says, as the collector read it

PHP2Shell: Haven't patched yet? Take these steps now to mitigate - ZDNET

Promoted by curator@php.newsroom from the source watch (vault oq9gflln, read from its pack copy 7r83qic5), page au/news/zdnet/tech-php2shell-php-patch-mitigation-critical-exploit, snapshot 20261023T232528Z. Copied byte for byte; every file's sha256 is in captures/20261023T232528Z/provenance.json and was re-checked against the watch's own hashes.

What the page says

_Curator's reading of the capture._

ZDNET (English), 23 October, by Charlie Osborne: 'PHP2Shell: Haven't patched yet? Take these steps now to mitigate'. It says the PHP Project issued more instructions to prevent 'an unlikely Remote Code Execution (RCE) vector', now recorded as CVE-2026-115560, which needs an unusual configuration and application-code setup, with the mitigation of session.upload_progress.enabled=0 until the next scheduled fixes. It quotes Wiz that the flaws include memory disclosure and unauthenticated RCE in PHP itself, that building the attack chain 'required an exceptionally complex chain of steps' that frontier AI models substantially eased, relays Amazon Threat Intelligence that exploitation attempts began four days before disclosure and that a threat actor tied to the attack chains is trying to deploy a Mirai-style botnet, Cloudflare's CEO that millions of attempts are recorded, and the NSA's advice to inventory PHP-reliant systems and prioritise patches. A Perforce Zend/OpenLogic manager says most distributions had patches within hours.

> According to Amazon Threat Intelligence, attempts to exploit P2P2Shell were already happening four days before the vulnerabilities were made public.

Why it is here

From the promotion queue (index/promote.json, priority 4): Mentions CVE-2026-109618/109619 or php2shell: "PHP2Shell: Haven't patched yet? Take these steps now to mitigate - ZDNET". Selected mechanically, not read by a person.

Capture notes

Language en-US. Nothing in the page addresses an AI or hides text from a reader.

Claims that cite it

No claim cites this source yet.

Events that cite it

No timeline event cites this source yet.

The bytes

capture 20261023T232528Z · HTTP 200 · https://www.zdnet.com/tech/php2shell-php-patch-mitigation-critical-exploit/
  • headers.json 276f952f0011570d373d3041ab0522b50a0ac07197280050d02dc9aca53ef652 941 bytes
  • page.html 01150fa744516c5f53f50ad997526dcf036d92ed805eb40a6d888cfd069b5931 257,460 bytes
  • provenance.json 4a152b50eab70aa3e04b7070e5b41c08283a262c9a3f386a5b988da8b90beca2 1,711 bytes
  • rendered.html 1bb6753f10db7b74b4591a48199fb0f059cde0f332b3c8ea4dd1779754c0ed48 1,199,569 bytes
  • screenshot.jpg 90d593a86c5230062bce6030ba08889007bfc2f95d2245059b129d5e23bf7fee 734,217 bytes
  • text.txt cad66ee951f86463df8335e3261055c92bbcc9b25fe32583ac45aa8a64508695 8,983 bytes

The captured files are held privately in the evidence vault and are not republished; the hashes above are what the vault recorded at capture time. Every source →