「PHP2Shell」脆弱性公表後に悪用試行が数百万件単位に増加したとCloudflareが報告、顧客向けには新ファイアウォールを開発して有効化 - GIGAZINE

「PHP2Shell」脆弱性公表後に悪用試行が数百万件単位に増加したとCloudflareが報告、顧客向けには新ファイアウォールを開発して有効化 - GIGAZINE

Promoted by curator@php.newsroom from the source watch (vault oq9gflln, read from its pack copy 7r83qic5), page jp/news/gigazine/news-20261023-cloudflare-stats-php2shell-attempts, snapshot 20261024T083755Z. Copied byte for byte; every file's sha256 is in captures/20261024T083755Z/provenance.json and was re-checked against the watch's own hashes.

What the page says

_Curator's reading of the capture._

GIGAZINE (Japanese), 23 October: Cloudflare reported that exploitation attempts, only thousands before the disclosure, exploded afterwards and reached the millions about 12 hours after it, and that it developed and switched on a new firewall protection for customers. It embeds the Cloudflare CEO's post of 22 October with the ladder of attempts and links Cloudflare's blog 'Cloudflare deploys protections against php2shell vulnerability'.

> 公表前は数千件程度だった悪用試行が公表後は爆増し、公表から12時間ほどで数百万件という単位に増加していたことをCloudflareが報告しています。

_Curator's translation:_ "Cloudflare reports that exploitation attempts, which were only in the thousands before the disclosure, soared after it and grew to the millions within about 12 hours of the disclosure."

Why it is here

From the promotion queue (index/promote.json, priority 4): Mentions CVE-2026-109618/109619 or php2shell: "「PHP2Shell」脆弱性公表後に悪用試行が数百万件単位に増加したとCloudflareが報告、顧客向けには新ファイアウォールを開発して有効化 - GIGAZINE". Selected mechanically, not read by a person.

Capture notes

Language ja. Nothing in the page addresses an AI or hides text from a reader.