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, la mise à jour ferme la faille, mais oblige à traquer les compromissions possibles - IT SOCIAL
Promoted from the source watch (pack copy 7r83qic5), snapshot 20261023T160435Z, queue priority 3 (mechanical selection by researcher@php.newsroom, read by the curator). IT Social (French), 23 October: the first exploitation attempts came four days before the coordinated disclosure, which shifts a company's response fr...
What it says, as the collector read it
PHP2Shell, la mise à jour ferme la faille, mais oblige à traquer les compromissions possibles - IT SOCIAL
Promoted by curator@php.newsroom from the source watch (vault oq9gflln, read from its pack copy 7r83qic5), page fr/news/itsocial/cybersecurite-cybersecurite-articles-php2shell-la-mise-a-jou, snapshot 20261023T160435Z. Copied byte for byte; every file's sha256 is in captures/20261023T160435Z/provenance.json and was re-checked against the watch's own hashes.
What the page says
_Curator's reading of the capture._
IT Social (French), 23 October: the first exploitation attempts came four days before the coordinated disclosure, which shifts a company's response from patching to investigating. Applying the 21 October update closes the door without saying whether someone got in meanwhile, so hunting for traces becomes the next step. It lists the fixed versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35.
> Appliquer la mise à jour du 21 octobre ferme la porte sans dire si quelqu’un est entré entre-temps
_Curator's translation:_ "Applying the 21 October update closes the door without saying whether someone has come in in the meantime"
Why it is here
From the promotion queue (index/promote.json, priority 3): Mentions CVE-2026-109618/109619 or php2shell: "PHP2Shell, la mise à jour ferme la faille, mais oblige à traquer les compromissions possibles - IT SOCIAL". Selected mechanically, not read by a person. Text also matches compromise/breach terms: check for a named organisation or cause.
Capture notes
Language fr-FR. Nothing in the page addresses an AI or hides text from a reader.
Claims that cite it
| Claim | Who says it | Status | Fact-check | Primary | Sources |
|---|---|---|---|---|---|
| As of 14:40 UTC on 25 October, no named organisation has said it was compromised through php2shell. Exploitation attempts are widely reported, in millions; Hadrian reports exploitation at scale and Patchstack received reports of incidents from hosting partners, neither naming a victim, and Patchstack's own telemetry showed only probing. Sophos withdrew an earlier success claim: its data showed scanning and a few failed attempts. A time-bounded absence, not a confirmed fact: it can only be true as of the last check, and it will change. Changed from "confirmed" on 22 October at the editor's request. Refreshed by the journalist on 24 October against the evidence vault at 1f38e70921b2: the named cases (GMO, ČVUT, DMM, Valtec) are now in the vault, and none of them states php2shell as the cause (Valtec retracted). The PHP Foundation's executive director: "to our knowledge, there has been no successful attempt at remote code execution" (The Verge). Luxembourg: no institution has announced an intrusion (Paperjam). Patchstack: incidents reported to it by hosting partners (Recorded Future) against "only probing attacks, with no hard evidence of breaches yet" in its own telemetry (PCMag); on the board for the fact-check desk. An anonymous startup owner's claim of stolen source code (Fortune) is unnamed and not attributed to the flaw. Sophos, via Cyber Security News: a correction at 21:21 UTC on 22 October withdrew an earlier success claim; scanning and a small number of failed attempts, a Mirai-derived payload blocked. American Banker, 23 October: no US bank or credit union has publicly reported a compromise. Refreshed on 24 October at 16:05 UTC against the vault at 8c16a64a7cf6 (382 sources): no new source names an organisation compromised through php2shell; Die Presse (12:03 on 23 October) knows of no successful attack in Austria, and RainForest's honeypot (VOIX) records attempts only. Refreshed again on 25 October at 09:35 UTC (09:35 GMT: the UK clocks went back at 01:00 UTC that day; an earlier version of this note said 10:35 BST, which was wrong) against the vault at 87795d121200 (418 sources): still no new source names an organisation compromised through php2shell; Turkey's Presidency Cybersecurity Directorate says the e-Devlet portal had no problem. Refreshed on 26 October against the vault at 94352a55fbaa (454 sources, latest capture 14:40 UTC on 25 October): 16 new claims reviewed, still no new source names an organisation compromised through php2shell; La Razón (23 October) knows of no successful execution. fact timeline → | this site, from every captured source in the evidence vault (454 sources, head 94352a55fbaa), as of its latest capture at 14:40 UTC on 25 October | reported | A4 Corroborated●●●●○○ | 6/24 | CISA CISA Huntress Amazon SecurityWeek SecurityWeek Recorded Future Imperva Threat Research Weird Gloop Paperjam PCMag IT Social Lupa.cz Yahoo! News Japan 産経ニュース INTERNET Watch The Verge Cyber Security News American Banker The Next Web Die Presse voix Haber.com La Razón |
Events that cite it
No timeline event cites this source yet.
The bytes
capture 20261023T160435Z · HTTP 200 · https://itsocial.fr/cybersecurite/cybersecurite-articles/php2shell-la-mise-a-jour-ferme-la-faille-mais-oblige-a-traquer-les-compromissions-possibles/
headers.jsondc4fcd9e93f05f21e466beaf11c106f736bd1683dd6027ea697b4cd9f556c476 880 bytespage.html7b87fccd00ca774f5357da48c1c26180992bb5f584e6a1b257f38340474fa313 360,599 bytesprovenance.json1475378758653e01c69ddd63ad965d6d1bb1da125c39740623868dc787fa6b81 1,919 bytesrendered.htmlb798e757871bfc8f6f9028b0f7a4df92dfbb6fcb1fbf4422745e6d569ce00c15 359,599 bytesscreenshot.jpgca7d82ca3ed331cf943625541100023f459ff78ed579076fe731751016a73a28 908,893 bytestext.txt192f86a7b6081dfb7c2813799068d074cef0b3c931f3957262fe715c09001b70 13,533 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 →