For managers and business owners

PHP2Shell: how to protect your company website in five steps

Servers have already been broken into through these flaws. This is the short guide: what to ask for, what to check and what to do if you can't update today.

Dinis Silva, founder of Nosis · · 4 min read

Why it can't wait any longer

In the first days there were attack attempts but no confirmed break-ins. That has changed. On 26 October, CISA added both flaws to its catalogue of exploited vulnerabilities and gave US federal agencies three days to fix them[1]. On the 29th, a campaign was disclosed that used PHP2Shell to take full control of 25 servers in the US and Asia, each in under 15 minutes[2].

That campaign targeted the firewalls of companies and public bodies. What it shows is speed: once someone decides to attack an unpatched server, the job takes minutes, not days.

Five steps to stay protected

  1. Confirm the real PHP version

    Ask whoever runs the site, whether an agency, a contractor or the hosting company, for the PHP version on the server, in writing. The WordPress, theme or plugin version doesn't matter: the flaw is in PHP, underneath all of that.

    Check my site in seconds →
  2. Update and restart

    The safe versions are 8.2.35, 8.3.36, 8.4.27 and 8.5.12, or later[3]. After updating, restart every PHP process. Without that, the old version keeps running[4].

  3. On PHP 8.1 or older, move to a supported version

    These branches no longer get official fixes. Extended-support vendors publish patches for old versions[5], but the lasting fix is moving to a supported release.

  4. If you can't update today, reduce the risk

    Temporary measures such as turning off session.upload_progressreduce the exposure but don't remove it[4]. If even that isn't possible, the UK's National Cyber Security Centre advises considering taking the system offline until it is fixed[6].

  5. Look for signs of intrusion

    In the confirmed attacks, the attackers left webshells, small files that let them get back in[7]. New or changed PHP files, unknown accounts in the admin panel and emails sent for no reason are warning signs.

Patching closes the door. It doesn't tell you whether someone already walked through it.

A message to send your provider today

If another company runs your site, copy this and send it. The reply tells you where you stand.

Ready to copy
Hello,

Following the PHP2Shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619), please confirm in writing:

1. The PHP version running on our website's server.
2. The date the fix was applied, and whether the PHP services were restarted.
3. Whether anyone has checked for signs of intrusion since 21 October.

Thank you.

If the reply is slow or vague, that's a sign someone should look at the server.

Frequently asked questions

My host says it has already updated. Is that enough?

If the confirmed version is one of the fixed ones (8.2.35, 8.3.36, 8.4.27, 8.5.12 or later) and the PHP services were restarted, the flaw is closed. What's left is whether anyone got in first: the earliest attack attempts predate the 21 October 2026 fix, so it's worth checking for signs of intrusion.

Does hiding the PHP version protect me?

No. Hiding the version stops others from seeing it, but the server is still vulnerable to PHP2Shell if PHP hasn't been updated.

Do I have to tell anyone if I was attacked?

If personal data was accessed, the GDPR may require you to notify your data protection authority within 72 hours of becoming aware of the breach.

Sources

  1. CISA Adds Two Known Exploited Vulnerabilities to Catalog (CISA, 26 Oct 2026)
  2. Suspected Chinese attackers built a custom PHP2Shell exploit and rooted 25 servers (The Register)
  3. CVE-2026-109618 and CVE-2026-109619: Critical Unauthenticated Remote Code Execution in PHP (Rapid7)
  4. PHP2Shell: detection, analysis, and remediation (Datadog Security Labs)
  5. php2shell patches now available for PHP 5.2 through 8.1 (TuxCare)
  6. Critical security issue affecting PHP (NCSC, UK)
  7. CISA warns of Fragnesia Linux flaw chained in PHP2Shell attacks (BleepingComputer)
Full diagnosis

Tell us which site. We'll tell you what to do.

Asking commits you to nothing: we reply first, and only go ahead with your agreement.

  1. 1
    We reply the same working dayWe confirm what you need and arrange the diagnosis.
  2. 2
    Full diagnosis: €150 + VATOn the server, with what we found and a fixed price for the fix.
  3. 3
    If you go ahead, the €150 is deductedYou only pay the difference.

Request a diagnosis

€150 + VAT, deducted if you go ahead with the fix. Your details are only used to reply to you.