A focused engagement to identify the exposed runtimes, choose a real fix, and verify it.
Who it is for
Teams who can give us shell or change-window access, or who want a plan their own admins will execute.
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
Inventory of web SAPIs, a chosen package or migration per runtime, a rollback note, and a verification record.
Limits
We do not promise a same-day in-place patch for every legacy branch. Where no vendor fix exists, the deliverable says so.
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.