dC0dez.

PHP Security Remediation Services

Critical PHP vulnerability? Start with the systems that may be exposed.

PHP security problems can affect websites, APIs, customer portals, and business applications.

Recent critical PHP runtime vulnerabilities make it important to identify the versions your applications actually use, determine exposure, and apply vendor-supported fixes.

dC0dez helps organizations review affected environments, prepare updates, validate compatibility, and plan longer-term remediation.

Request PHP Security Help

What happened in October 2026?

On 21 October 2026, the PHP security team released fixes for two critical vulnerabilities:

  • CVE-2026-109618
  • CVE-2026-109619

These vulnerabilities can allow unauthenticated remote code execution on affected PHP web runtimes.

The first fixed releases were PHP 8.2.35, 8.3.36, 8.4.27, and 8.5.12.

A further vulnerability, CVE-2026-115560, was reported separately and requires attention to its own advisory and applicable remediation guidance.

Security notice: This information is current as of 27 October 2026. Review official PHP and vendor advisories for the latest guidance.

Our PHP security assessment covers

  • PHP runtime discovery and version inventory
  • Review of affected web-facing deployments
  • Dependency, framework, and configuration review
  • Relevant vulnerability assessment
  • Patch and upgrade planning
  • Application compatibility assessment
  • Regression testing requirements
  • Deployment and rollback planning
  • Residual risk documentation
  • Recommendations for ongoing maintenance

What if you use an unsupported PHP version?

Older PHP releases may no longer receive upstream security updates.

We assess whether the application can be upgraded to a supported runtime or whether a broader modernization or migration project is appropriate.

Vendor-maintained PHP distributions may have separate patching arrangements. Those must be verified against the vendor's own security notices.

A patch is important. So is validation.

Production upgrades can affect application behavior, extensions, frameworks, and integrations.

Our remediation approach considers both the security issue and the work required to update the application safely.

If unauthorized access or compromise is suspected, incident investigation and recovery need a separately agreed scope and qualified handling.

Frequently asked questions

What is PHP2Shell?

PHP2Shell is the name used for two critical PHP runtime vulnerabilities disclosed in October 2026.

Does updating WordPress or Laravel fix PHP2Shell?

Updating a framework or CMS does not establish that the underlying PHP runtime has been patched. Both layers need appropriate attention.

Does a web application firewall solve the problem?

A firewall may provide partial protection in some circumstances. It does not replace the required security update.

Can you guarantee that a patched application has not been compromised?

No assessment can establish that solely from the patch version. Evidence of compromise requires appropriate investigation.

Need to address PHP security risk?

Tell us what you know about the application, PHP version, and hosting environment.

Request PHP Security Help

REQUEST AN ASSESSMENT

PHP security enquiry

Tell us about your application. Do not send passwords, access tokens, or confidential application data.

[PLACEHOLDER: Configure Turnstile public site key in site-config.json]