php2shell
for security engineers, devops
Why this scored 32
every term, weightedIts fastest-moving item, measured against the pace of its own source
Whether that velocity is itself speeding up, as a per-hour rate
How many independent communities its own items come from
Decays to zero over 14 days, counted from when we first saw it
Subtracted once something is big and old — sized by its biggest item, aged from when we first saw it
Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On an entity's first sighting there's no previous reading to compare against, so acceleration starts from a neutral prior rather than a measurement, and velocity falls back to engagement over its whole lifetime until a second reading exists. Full methodology
Outlook
low confidence · estimate, not a guarantee7-day
~59
range 17–70
14-day
~64
range 20–78
30-day
~66
range 17–86
Signal history
7-day window (free)projected trajectory (estimate, not a guarantee)
The evidence
The live items this entity's score aggregates — every community independently talking about it right now. This is the corroboration, shown, not claimed.
- 145
php2shell by Calif Research
Calif Research releases php2shell, highlighting new security risks for PHP sites. · for security engineers, php admins
lobstersEmerging 2 · php2shellsecurity3d ago - 231
PHP vulnerability PHP2Shell: what the October 21 emergency release fixed and what is still disputed
Emergency release patches PHP2Shell flaw; some aspects remain contested. · for web developers, security engineers
devtoSteady 2 · wordpresssecurity2d ago - 331
Patch Your PHP: What PHP2Shell Means for WordPress Sites
PHP2Shell vulnerability can let attackers execute code on WordPress sites. · for web devs, security engineers
devtoSteady 2 · wordpresssecurity1d ago - 419
Testing the AWS WAF Mitigations for PHP2Shell on Both CloudFront and an ALB
Shows how to test AWS WAF mitigations against PHP2Shell attacks on CloudFront and ALB. · for security engineers, cloud admins
devtoSteadysecurity1d ago - 518
PHP2Shell: Your Code Was Fine, The Engine Was Not
Reveals engine-level flaws that affect PHP applications despite clean code. · for php devs, security engineers
devtoSteadysecurity1d ago - 618
PHP2Shell, explained: the two critical PHP bugs every team needs to patch
Patch PHP2Shell bugs to prevent remote code execution. · for security engineers, devops
devtoSteadysecurity2d ago - 717
PHP2Shell: AI uncovers critical RCE in PHP
AI discovered a critical remote code execution flaw in php2shell affecting PHP applications. · for security engineers, php devs
hackernewsSteadysecurity3d ago - 817
Amazon identifies Oct 17 PHP2Shell exploitation prior to public disclosure
Amazon disclosed early detection of PHP2Shell exploit, prompting timely patches. · for security engineers, devops
hackernewsSteadysecurity2d ago - 915
php2shell-CVE-2026-109618-CVE-2026-109619-PoC — Proof-of-Concept (PoC) exploit for php2shell (CVE-2026-109618 / CVE-2026-109619), demonstrat
PoC reveals remote code execution vulnerability in php2shell, requiring immediate patching. · for security engineers, php developers
githubSteadysecurity2d ago - 1015
php2shell-bypass-aslr-exp — A php2shell exploit that requires no modifications to the official version, and does not require display_errors
php2shell exploit bypasses ASLR without altering core or needing display_errors. · for security engineers, penetration testers
githubSteadysecurity2d ago