Security · Cardiff & UK

PHP2Shell assessment & patching

Find affected PHP runtimes. Apply the fix. Verify what is running.

Starting price
From £375 + VAT
Best for
PHP sites and applications affected by the October 2026 security release
Leaves you with
An exposure record, patch evidence and verified application checks
Scope & timing
Urgent work is assessed against current availability. We agree the response window after triage; this is not a 24/7 incident hotline.

A clear scope. A useful outcome.

PHP2Shell is the name associated with CVE-2026-109618 and CVE-2026-109619, disclosed in October 2026. An affected PHP runtime needs attention even when the application itself has not changed. We help establish which sites, servers, containers and installed PHP versions need a fix, then coordinate a controlled update with your team or hosting provider.

A vulnerability alert is not proof of a breach. We keep exposure assessment, patch verification and suspected-compromise investigation separate. If there are signs of unauthorised access, we prioritise preservation of logs and evidence and agree containment before treating an update as the whole recovery plan.

  • An inventory of in-scope PHP runtimes, applications and hosting responsibilities.
  • Affected-version checks against upstream or hosting-provider advisories, including vendor backports.
  • An agreed change plan with a verified backup and a safe recovery approach.
  • Runtime updates and necessary process restarts, followed by application and worker checks.
  • A written record of the applied fixes, running versions, validation results and unresolved exposure.

How the work runs.

  1. Triage the exposureConfirm ownership, hosting, installed versions and the applications served by each runtime. Review signs of compromise and identify dependencies that may block a direct update.
  2. Plan the changeAgree access, backup checks, a maintenance window and host responsibilities. Where an immediate patch is blocked, discuss isolation with the system owner while the permanent fix is arranged.
  3. Apply and restartApply the appropriate upstream or vendor security release. Check web-serving processes and long-running application workers so an updated package is not mistaken for an updated running service.
  4. Verify and recordCheck the runtime actually serving requests, exercise critical journeys and review errors. Record the evidence and any remaining actions for the owner of each system.

Agree the boundaries first.

  • Applying a patch addresses the specified vulnerability; it does not establish that an existing compromise has been removed. Subsequent vendor guidance may require further action.
  • Third-party hosting access and provider-controlled changes remain dependencies. Response and completion times are agreed after assessment.

Questions before we start.

Which PHP versions contain the PHP2Shell fixes?
PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 were the upstream security releases on 21 October 2026. That is the original release baseline: we also check later vendor guidance, including PHP's 23 October session-upload-progress notice. Vendor backports can use different version strings, so package evidence matters alongside the displayed version.
Does updating WordPress fix PHP2Shell?
A WordPress core update alone does not replace the underlying PHP runtime. The host or server administrator must apply the relevant PHP fix, with compatibility checks for the site, its plugins and its theme.
Can a firewall replace the PHP update?
Do not treat a firewall rule or temporary configuration change as equivalent to the vendor fix. The engagement focuses on applying and verifying the appropriate security release; interim containment is considered only while that work is arranged.
What should I send with an urgent enquiry?
Send the site URL, hosting provider, known PHP versions and a brief description of the issue or alert. Do not put passwords, private keys, customer records or full logs in the contact form. We agree a suitable access route after triage.

Work directly with QDev

Tell us what needs to change.

Name, email and a project message are required.

10 to 2,000 characters. Include the goal, current state and any deadline.

We use your details to assess your enquiry and reply. Read our privacy note.

PHP development

Laravel upgrades & security

Laravel upgrade and security work for live applications. QDev reviews PHP, Composer dependencies, Forge servers, queues and deployment checks as one system.

You leave with An agreed upgrade implemented and checked across web and background work

Price From £1,850 + VAT

Explore Laravel upgrades & security

Security

Hacked website recovery

Assess recovery for a compromised PHP or WordPress site with QDev. Scope containment, evidence preservation, restoration, credential changes and hardening.

You leave with A documented recovery, agreed validation and a follow-up security plan

Price From £475 + VAT

Explore Hacked website recovery

Start with the facts.

Send the site, the hosting provider and what has changed. We'll reply with the next step and what it depends on.