The challenge for many organisations will be identifying everywhere PHP is running. Potential exposure may extend across:
- Public websites and customer portals
- Internal business applications
- Content management and e-commerce platforms
- Web-based administration tools
- Hosted and managed services
- Products or appliances that embed PHP
- Legacy applications
- Systems managed by hosting providers, agencies or other suppliers
This means the review should not be limited to your main website. Application owners, development teams, hosting providers and technology suppliers may all need to be involved.
What should organisations do now?
Identify affected systems
Establish where PHP is being used across public, internal and supplier-managed systems. Record the installed version, application owner, hosting arrangement and business importance of each service.
Apply the appropriate security updates
The PHP Project has released PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12 to address the vulnerabilities. Organisations should upgrade to the appropriate fixed release or apply an equivalent package supplied by their Linux distribution, hosting provider or product manufacturer.
PHP 8.1 and earlier are no longer supported by the upstream PHP Project. Organisations using these branches should confirm the availability of an appropriate fix with their distribution or long-term support provider and plan a move to a supported release.
Validate the outcome
After updating affected systems, confirm that the patched version is installed and active. Where appropriate, complete a targeted exposure assessment and rerun the assessment following remediation. Version information and assessment results should be reviewed together. Servers may hide their PHP version, while suppliers can sometimes backport security fixes without changing the main version string. A clean result also only applies to the systems included within the authorised scope.
Continue monitoring
Review web-server, PHP, proxy and endpoint telemetry for unusual requests, unexpected processes, file changes and other suspicious activity. Web application firewall rules and other temporary measures may help reduce particular attack paths, but they should support rather than replace patching.
How Storm Technologies can help
Understanding your PHP2Shell position requires more than checking one website or running a simple version scan.
Storm Technologies can help you identify where further investigation may be needed, define the right scope for an exposure assessment and interpret the findings in the context of your environment.
We can also help your teams prioritise affected systems and determine the appropriate next steps across applications, infrastructure and cyber security.
Concerned about your PHP2Shell exposure?
Speak to a Storm Technologies security specialist. We can help you review the potential risk, identify where further investigation is required and agree the most appropriate next steps.