HackSpotby Amethyst Apps
How it worksWhat we checkPricingGuidesInsightsAbout
Log inCheck my website
HackSpot / Insights

PHP2Shell: what to ask your web host (copy-and-paste email)

A free, ready-to-send email asking your web host to confirm the PHP2Shell fixes, plus the five questions to ask and how to read their reply.

By HackSpot team (Amethyst Apps) · October 23, 2026 · 3 min read

HackSpot: what to ask your web host about PHP2Shell

The short version: for most small businesses, fixing PHP2Shell is your web host's job. Your job is to get a clear "yes, it's done" in writing. Copy the email below, add your website address and send it today. If you're not sure which version you're on, run a free check first.

The email

Copy this and send it to your hosting company's support desk, or to the web developer or agency who looks after your site:

Subject: Please confirm PHP2Shell fixes (CVE-2026-109618 and CVE-2026-109619) for [your website address]

Hello,

On 21 October 2026 the PHP project released fixes for two critical
flaws, CVE-2026-109618 and CVE-2026-109619 (known as PHP2Shell).

For our website [your website address], please could you confirm:

1. Which PHP version and release the site runs (for example 8.3.36).
2. That it includes the fixes: 8.2.35, 8.3.36, 8.4.27, 8.5.12 or later,
   or a vendor package with the fixes backported.
3. That PHP was restarted after the update.
4. If the site is on PHP 8.1 or older, what you are doing about it
   and when we can move to a supported version.
5. Whether you have checked for any signs of compromise.

Thank you.
[Your name]
[Your business]

How to get a clear answer from your host

  1. Send the email from the address your hosting account uses. Support teams can act faster when they can match you to the account.
  2. Include your website address and, if you have one, your account or customer number. Never include your password; a real support team won't ask for it by email.
  3. Ask for the answer in writing. A short written reply is useful if your insurer, a client or an auditor asks later.
  4. Read the reply against the checklist below. If anything's missing, reply and ask again, politely.
  5. Run a free check again afterwards. HackSpot's free check shows whether your site still reports an older PHP version publicly.

How to read the reply

A good reply names the release (for example "PHP 8.3.36") or confirms the host's own package includes the fixes for both CVEs, and says PHP was restarted.

"We're on PHP 8.3" isn't enough: 8.3 is the branch, and only 8.3.36 and later include the fixes. Ask for the release.

"Our servers are patched" with no detail is common during busy weeks. It's reasonable to ask which release or package is in use.

"You're on PHP 7.4 / 8.0 / 8.1" means your site is on a branch past end of life. Ask whether they've applied a backported fix and when you can move up. Read why old PHP versions matter now.

No reply within a couple of working days: chase by phone. If your host manages many sites, they'll be busy, but critical fixes should be a priority.

Why the version your site shows might be "wrong"

Many Linux distributions and hosts apply security fixes to their own PHP packages without changing the version number your site reports. That's why an older-looking number means "ask", not "vulnerable".

If you manage your own server

If nobody else looks after your server, the job is yours. The PHP project's advice is to update to the fixed release for your branch, restart every PHP worker, and use temporary measures only as a stopgap, because they don't make an installation safe. The UK's NCSC also suggests checking any system you couldn't update straight away for signs of compromise.

Questions people ask

Who should I send this to?

Whoever controls your server's PHP: usually your hosting company. If an agency or freelance developer manages your hosting, send it to them.

Do I need to know anything technical?

No. The email asks the right questions for you. The checklist above helps you tell a complete answer from a vague one.

My host says it's fixed but my site still shows an old version. Who's right?

Possibly both. Hosts often patch without changing the number. If they confirm in writing that the fixes are in place, that's the answer that counts.

Should I also ask my other suppliers?

It's sensible to ask suppliers whose systems hold your data, such as your CRM or booking system. Ask whether they've applied the PHP fixes and whether your data is affected.

Can HackSpot send the email for me?

No, you send it yourself so the reply comes to you. Every HackSpot report includes a ready-made message like this for each finding.

More on PHP2Shell

  • PHP2Shell: what small businesses need to do today
  • How to check which PHP version your website runs
  • Is my WordPress site affected by PHP2Shell?
  • When your suppliers go down

Sources

  • PHP security advisory, 21 October 2026 (php.net)
  • Critical security issue affecting PHP (NCSC)
  • PHP2Shell exploitation and response (watchTowr)
  • Supported PHP versions (php.net)

Check your website free

See what your website shows the world in about a minute: a plain-language report, who should fix each thing, and a message to send them.

Check my website

Free to check

See what your website shows the world.

Check my website free
HackSpotby Amethyst Apps

Plain-language security checks for your website and the suppliers your business depends on.

HackSpot

  • How it works
  • What we check
  • Free check
  • Pricing

Resources

  • Guides
  • Insights
  • Supplier status

Help

  • About
  • Security
  • Contact us

Amethyst Apps

  • All apps
  • IndexStream
  • Partners

© 2026 Amethyst Apps. Built in the UK.

2G, Ingram House, 227 Ingram Street, Glasgow, G1 1DA, United Kingdom

PrivacyTermsCookiesSecuritySitemapPartners
EnglishEspañolFrançaisDeutschItalianoPortuguêsNederlandsPolskiSvenska日本語
HackSpot