ثغرات PHP تفتح الباب للقراصنة.. هل موقعك الإلكتروني محمي؟ – شبكة بلجيكا 24 الإخبارية

ثغرات PHP تفتح الباب للقراصنة.. هل موقعك الإلكتروني محمي؟ – شبكة بلجيكا 24 الإخبارية

Promoted by curator@php.newsroom from the source watch (vault oq9gflln, read from its pack copy 7r83qic5), page eg/news/belg24/d8-ab-d8-ba-d8-b1-d8-a7-d8-aa-d8-a8-d9-8a-d8-a5-d8-aa-d8-b4, snapshot 20261029T094207Z. Copied byte for byte; every file's sha256 is in captures/20261029T094207Z/provenance.json and was re-checked against the watch's own hashes.

What the page says

_Curator's reading of the capture._

An Arabic-language Belgian news-network article (Belgium 24, 23 October) in which the outlet's technical team reports on a check of its own server environment after the PHP security updates: it analysed 73,306 files, matched core WordPress files against official lists, reviewed web logs and file permissions, confirmed the updates were applied in the environment checked, found no malicious files, and corrected 385 files whose permissions let 'others' write, with the SHA-256 hashes of the 382 files in the second batch compared before and after to show contents were untouched. It also restates, citing a joint European statement and the PHP foundation, that the two flaws may allow remote code execution and score 9.2, and that updating WordPress alone does not fix them.

> ولم تسجل أداة الكشف ملفات خبيثة ضمن التحليل المنفذ.

_Curator's translation:_ "The detection tool recorded no malicious files in the analysis performed."

Why it is here

From the promotion queue (index/promote.json, priority 4): Mentions CVE-2026-109618/109619 or php2shell: "ثغرات PHP تفتح الباب للقراصنة.. هل موقعك الإلكتروني محمي؟ – شبكة بلجيكا 24 الإخبارية". Selected mechanically, not read by a person.

Capture notes

Language ar. A self-report about one outlet's own server, not an independent finding about the incident. Nothing in the page addresses an AI or hides text from a reader.