Trace Nginx server blocks to PHP-FPM and make the PHP change without confusing it for an Nginx CVE.
Who it is for
Sites where fastcgi_pass targets are undocumented or duplicated across includes.
PHP2Shell remediation for every PHP version, including PHP 5.6 and legacy environments, is in scope when you need it. Still running PHP 5.6, PHP 7.x, or an unsupported release? The work is to evaluate a real fix and avoid an unnecessary outage. It is not a claim that every version has a vendor patch.
What you receive
A vhost-to-socket map and a patch sequence that restarts FPM.
Limits
We do not sell a generic Nginx hardening bundle as the PHP2Shell fix.
No customer counts, certifications, or response-time promises are stated because none are configured. Contact details are on the contact page and only work once an email or booking URL is set.
How an engagement usually moves
- Assess the environment you can show us.
- Identify the safest supported fix, or say that none is published.
- Implement with a rollback, or hand the plan to your admins.
- Validate the running SAPI.
Discuss the estate from the contact page.
Questions
How much does this cost?
Pricing is not published. It depends on how many runtimes and applications are in scope.