Find web interfaces, review PHP evidence, and plan the next update. Your scan runs on this computer.
01 / Choose your scope
Where should we look?
Scanning your selected targets
Filtered or offline addresses may need the full timeout. Stopping saves the evidence collected so far.
Latest web responses
Up to 10 recent findings. The complete report is saved when the scan finishes or is stopped.
02 / Review the evidence
Findings and next steps
Run a scan or open the sample to see results here.
Sample data. These are fictional findings, not results from your network.
A missing PHP header is not a clean result. Vendor backports and the actual web-serving runtime must be verified.
Not disclosed = PHP indicators without a version. Not detected = no PHP evidence. Not assessed = no usable application page. TLS certificate blocks are included in the default view; product branding is not a PHP version.
Priority
Device
PHP
Evidence / next step
03 / Make the right update
Match the update to the device.
Use the report to prioritize. Confirm the exact server runtime or appliance firmware before changing it.
01
Debian / Ubuntu servers
Copy the included update-debian-ubuntu.sh to the ordinary server you administer. Preview with:
bash update-debian-ubuntu.sh
After reviewing its plan, backup and maintenance window:
sudo bash update-debian-ubuntu.sh --apply
The helper asks before changes. Verify the available packages fix both CVEs. Package hooks may restart services.
02
Windows / IIS
Use the included windows-inventory.ps1 to find common PHP installations and readable IIS mappings. Then install the matching vendor build.
Check architecture, thread safety, extensions and configuration. Verify the active web runtime after restarting affected workers.
03
NAS, firewalls & appliances
Use your vendor's firmware or product update. Do not run the generic Linux helper on a vendor-managed device.
Restrict exposed management interfaces. For containers, rebuild and redeploy the affected images.
Verify after updating. A banner or package-manager success cannot prove remediation. Check vendor backports, restart all affected workers, test the application, and rescan. Preserve logs and investigate separately if compromise is suspected.