Determine whether Apache embeds mod_php or proxies to FPM, then patch the right process.
Who it is for
Hosts that grew from mod_php and may still have it on one vhost.
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
Module evidence, the package to update, and the restart that unloads the old module.
Limits
Moving off mod_php can be part of the plan. It is not required to install a patched module you already have.
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.