VulnRadar – PHP vuln response board

Helps small teams tell whether they were actually hit during a vuln window

Problem

When a PHP vulnerability drops, orgs of all sizes scramble to patch, find PoCs, and reproduce. Afterwards everyone wants to know: was it exploited? Public defacements and takeover warnings are scarce, so admins guess—and can't give their team or clients an evidence-based answer.

Solution

A lightweight vulnerability response board: users log their PHP versions and internet-facing services; the tool aggregates public exploitation signals, patch status, and a checklist, then generates a shareable 'checked / no signs found' report so teams align and leave a paper trail during the window.

Users

SMB sysadmins, freelance site builders, and developers who must report security posture to clients

MVP

Log PHP versions and public service inventory; built-in checks and patch status for known vulns; curated links to public exploitation signals; exportable investigation report; follow-up reminders

Revenue

Team subscription with white-label report export; free tier limited to one project

Why now

PHP still powers many small sites, and information chaos during vuln windows recurs. No license or massive dataset needed—curated public info plus a structured workflow is enough to start.