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: des milliers de sites exposés au Luxembourg | Paperjam News
Promoted from the source watch (pack copy 7r83qic5), snapshot 20261023T160435Z, queue priority 3 (mechanical selection by researcher@php.newsroom, read by the curator). Paperjam (French, Luxembourg): thousands of sites are exposed in Luxembourg. The two flaws are rated 9.2 out of 10 and sit in the PHP engine itself, n...
What it says, as the collector read it
PHP2Shell: des milliers de sites exposés au Luxembourg | Paperjam News
Promoted by curator@php.newsroom from the source watch (vault oq9gflln, read from its pack copy 7r83qic5), page lu/news/paperjam/article-php2shell-des-milliers-de-sites-exposes-au-luxembour, 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._
Paperjam (French, Luxembourg): thousands of sites are exposed in Luxembourg. The two flaws are rated 9.2 out of 10 and sit in the PHP engine itself, not in a WordPress extension or a badly kept site; WordPress, Drupal, Joomla, Magento, WooCommerce, Symfony, Laravel, Nextcloud and Roundcube can be affected. No Luxembourg financial institution, public service or operator had announced it had actually been infiltrated; authorities ask operators to look back for traces of compromise and to preserve evidence.
> Aucun établissement financier, service public ou opérateur luxembourgeois n’a cependant annoncé avoir été effectivement infiltré par PHP2Shell.
_Curator's translation:_ "No Luxembourg financial institution, public service or operator has however announced having been actually infiltrated by PHP2Shell."
_The watch reader's summary (researcher@php.newsroom, of its snapshot 20261022T171501Z, not necessarily this one):_ Paperjam reports that Luxembourg's state IT centre (CTIE) preventively made some services unavailable and that the cyber-risk cell met twice. The CSSF told financial entities to treat all PHP services as exposed. Local exposure estimates range from over 5,000 sites (per the LHC director) to about 10,600 PHP and 15,177 WordPress sites (per BuiltWith).
Why it is here
From the promotion queue (index/promote.json, priority 3): Mentions CVE-2026-109618/109619 or php2shell: "PHP2Shell: des milliers de sites exposés au Luxembourg | Paperjam News". Selected mechanically, not read by a person. Text also matches compromise/breach terms: check for a named organisation or cause.
Capture notes
Language 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://paperjam.lu/article/php2shell-des-milliers-de-sites-exposes-au-luxembourg
headers.json2224804391f9039f9c3b3b8f9e69bfc0078a9b68b20731ea3536d5de439e6cc6 1,049 bytespage.html0e5257c13c396617b977794021ed67914b1b48fe67e99643852efc8abcaa4e5e 162,673 bytesprovenance.jsonfd1670a04f377f14d3fa93b4017bed37541143fbb9bac35e6fa7ddb7cf5a06f8 1,598 bytestext.txt73aed7ccd645b7172699b36b2e9dd8540c0300f2ff6c3de8ad218d7aeb29b20e 14,203 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 →