Edition of Tuesday 27 October 2026

PHP2Shell: No login, no app code, no warning. What next?

Comments on “PHP2Shell: No login, no app code, no warning. What next?”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

Two critical PHP core flaws, CVE-2026-109618 and CVE-2026-109619 ("PHP2Shell"), reportedly let an unauthenticated attacker run code through a crafted web request. Each is rated CVSS v4.0 9.2, and all earlier releases are affected. Fixes are in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35; 7.4, 8.0 and 8.1 get only source backports. watchTowr reports honeypot exploitation, while other telemetry shows mostly probing. The claims come from a vendor post without cited sources, so the hard task is inventorying every PHP install.

Read the original at theregister.com. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 5 of 124 with a score of 0.75. The panel rated it highest on practical relevance (0.93) and reader interest (0.88), lowest on new information (0.55). The judges disagreed most on new information (spread 0.68), so the story is marked contested.

Every answer behind this is in the table under Score.

Score

0.75total under rubric v2.2Contestedjudges differ by 0.68 on new information

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.76
  • Reader interest0.88
  • Audience breadth0.69
  • Practical relevance0.93
  • Substantiated0.61
  • Technical depth0.59
  • New information0.55
  • Counts against: Promotional0.05
  • Counts against: Overclaim0.35

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
Significance0.760.750.780.760.03+0.24+0.183
Reader interest0.840.900.900.880.06+0.26+0.229
Audience breadth0.700.750.620.690.13+0.13+0.090
Practical relevance0.940.950.900.930.05+0.22+0.204
Substantiated0.430.700.700.610.27+0.05+0.030
Technical depth0.630.600.550.590.08+0.05+0.030
New information0.730.800.120.550.68 , above the contested threshold+0.05+0.028
Promotional0.070.050.020.050.05−0.19−0.009
Overclaim0.500.200.350.350.30−0.11−0.038
Sum of contributions+0.746
Claim-check penalty0.000
Total, as published0.746

Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.

The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

Ranked #5 on Rubric, 27 Oct 2026
<a href="https://rubric.hrih.si/editions/2026-10-27/5/"><img src="https://rubric.hrih.si/badge/2026-10-27/5.svg" alt="Ranked #5 on Rubric, 27 Oct 2026" width="238" height="28"></a>

Claim check

Claim check: 8 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. No source givenVersion

    PHP fixed releases for the PHP2Shell flaws are 8.5.12, 8.4.27, 8.3.36 and 8.2.35.

    The article gives no link or citation for it.

    The article says

    “Fixed versions: 8.5.12, 8.4.27, 8.3.36 and 8.2.35”

    The source says

    No source to compare with.

  2. No source givenCausal conclusion

    CVE-2026-109618 and CVE-2026-109619 (PHP2Shell) let an unauthenticated attacker run code on a server with a crafted web request.

    The article gives no link or citation for it.

    The article says

    “let an unauthenticated attacker run code on a server with nothing more than a crafted web request”

    The source says

    No source to compare with.

  3. No source givenNumber

    Both PHP2Shell CVEs carry a CVSS v4.0 score of 9.2.

    The article gives no link or citation for it.

    The article says

    “Both carry a CVSS v4.0 score of 9.2”

    The source says

    No source to compare with.

  4. No source givenGeneralization

    Every earlier PHP release is affected by the flaws.

    The article gives no link or citation for it.

    The article says

    “every earlier release is affected”

    The source says

    No source to compare with.

  5. No source givenDate

    The PHP security team shipped fixes within about a day of announcing the flaws after details leaked before the planned embargo.

    The article gives no link or citation for it.

    The article says

    “Details leaked before the planned embargo, so the PHP security team moved fast and shipped fixes within about a day of announcing them”

    The source says

    No source to compare with.

  6. No source givenDate

    watchTowr reports exploitation in its honeypot network as of October 21.

    The article gives no link or citation for it.

    The article says

    “watchTowr reports exploitation in its honeypot network as of October 21”

    The source says

    No source to compare with.

  7. No source givenQuote

    Tenable relays Cloudflare's CTO saying Cloudflare is seeing early attacks.

    The article gives no link or citation for it.

    The article says

    “Tenable relays Cloudflare's CTO saying Cloudflare is seeing early attacks”

    The source says

    No source to compare with.

  8. No source givenNumber

    Neither CVE is in CISA's KEV catalog yet, and no public indicators of compromise have been released.

    The article gives no link or citation for it.

    The article says

    “Neither CVE is in CISA's KEV catalog yet, and no public indicators of compromise have been released”

    The source says

    No source to compare with.

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN —

Recorded for context only, checked 27 Oct 2026, 05:46 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. This one was scored under rubric v2.2; How ranking works describes the current rubric, v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “PHP2Shell: No login, no app code, no warning. What next?”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.