PHP2Shell exposure sweep
Scan all your sites at once for known PHP/Node RCE exposure
- Problem
- When a PHP2Shell-style vulnerability lands, ops teams and small shops have a pile of sites and servers but no idea which versions are affected or which response headers leak the version. Existing tools only check a single endpoint, with no full-asset sweep. The exit of a global SSL/TLS certificate vendor also raises dependency-chain worries.
- Solution
- Input a list of domains or assets, asynchronously batch-check HTTP response headers, fingerprint PHP/Node versions, compare against known fixed releases, and output a report with severity and remediation advice—plus scheduled rescans and webhook alerts.
- Users
- Small-team ops, indie developers, freelancers hosting many sites
- MVP
- Bulk import domains with concurrent async scanning; fingerprint PHP/Node versions; compare against known fixed releases; shareable HTML report; webhook notifications
- Revenue
- Subscription by number of assets scanned, or a one-time local license; enterprise tier adds scheduled scans and self-hosting
- Why now
- During a vulnerability outbreak small teams lack commercial scanning budgets, and open-source scripts only check single points; the fingerprinting logic already exists and an indie can ship it in weeks
Source discussions · 3
- Hacker NewseMudhra to Exit Global SSL/TLS Certificate Business;103↑ 41
- Hacker NewsShow HN: Php2ShellCheck – Python script that checks for vuln indicators2↑ 0
- Hacker NewsShow HN: Blastradius – find PHP2Shell, Node, emSign or leaked tokens1↑ 0