PHP2Shell · website support

Not sure whether your website is protected from PHP2Shell?

We can help establish your hosting’s patch status, agree any necessary updates and check your website afterwards. Alongside your developer, hosting provider or internal team.

You don’t need to know your PHP version to get in touch.

Why your hosting needs checking

A website update starts
below the website.

PHP is server software used by many websites. PHP2Shell refers to two critical flaws that can let an attacker run code without logging in. Checking the software your host actually runs is the starting point.

A CMS update and a PHP update are separate tasks. Ask for confirmation from the person responsible for your hosting.

Something you can do now

Start with your hosting provider.

Send this to your host or developer. If they confirm the necessary work is complete, you may not need further remediation support.

A message for your host

Please confirm whether the PHP runtime serving my website has fixes for CVE-2026-109618 and CVE-2026-109619. Please identify the installed package or build and confirm the updated runtime is active. Have you also reviewed PHP’s 23 October session upload progress notice for my configuration? Please let me know if I need to take any action.

Not sure what their answer means? Talk it through with us →

Practical support

Understand. Update. Verify.

01 / Assess

Establish the position.

Identify the hosting, active PHP runtime and patch evidence. Understand which websites need attention and what remains uncertain.

Your outcome: a clear assessment and next steps.

02 / Update

Agree and carry out the work.

Coordinate with your host or update authorised infrastructure. Agree compatibility checks, backups and a maintenance window first.

Your outcome: agreed changes, carried out with care.

03 / Verify

Check and hand over.

Confirm the intended runtime is active. Test agreed journeys such as forms, sign-in or checkout, and document remaining actions.

Your outcome: a record of changes and checks.

Scope, availability and price are agreed before work begins. Suspected compromise needs separate incident triage.

Alongside your team

IT expertise. Business understanding.

Our team brings over 100 years of combined experience across IT, business and technology projects. We work with the people who know your systems and agree responsibilities from the start.

Meet the team →

Your questions

A clearer next step.

I use WordPress. Is this relevant?

PHP runs many WordPress and WooCommerce sites. Ask your host to check the runtime serving your website. Updating WordPress, themes or plugins is separate from updating PHP.

My host manages updates. Do I still need help?

Start by asking your host to confirm the installed build and that its fixes are active. If they have completed the necessary work, you may not need a separate engagement.

Can you help with several websites?

Yes. Tell us how many websites and hosting providers are involved so we can agree the scope together.

Can you tell from my website address?

A public URL alone cannot reliably establish patch status. Verification may need provider confirmation or authorised access. Sending an enquiry does not authorise testing or changes.

How much does help cost?

We agree scope, availability and price before technical work begins. An initial conversation does not commit you to an engagement.

What if I think my website has already been hacked?

Contact your host or existing incident responder promptly and preserve available logs. Suspected compromise needs separate incident triage: applying a patch does not show that a website was never compromised. Our enquiry form is not a monitored emergency service.

Get practical help

Tell us which website
you need help with.

Share your website address and what you know about the hosting. “Not sure” is a useful starting point.

Get help with my website →

We’ll review your enquiry and discuss scope and availability.