Security

PHP2Shell: Patching is mandatory. Modernizing is the opportunity.

Your IT reports: our website runs on PHP, and there is a critical flaw. What does that mean for the business, how fast do we have to react, and how do we make sure that next time we are not stuck waiting again? A briefing for decision makers, with a pinch of .NET bias.

In plain words

A crack in the foundation, not in the roof

PHP is the programming language that WordPress, TYPO3, Drupal, Joomla and many other CMS run on. PHP2Shell is not a bug in a plugin or in one particular CMS, it sits in PHP itself, in every version since 5.4 from 2012. An attacker needs no password: a crafted request to your website can be enough to run their own code on your server. Experts rate it as critical (CVSS 9.2 out of 10).

What it can mean for your business

  • Strangers take over your website

    Attackers can change content, serve malware to your visitors or plant fake forms. Under your name.

  • Data leaks out

    One of the flaws can expose the server's memory: passwords, sessions, API keys. With those, attackers often get further than the website, into the CRM or other connected systems.

  • Trust and obligations

    An incident on your website is public. If personal data is affected, a duty to report under the Swiss FADP or the GDPR can apply.

  • Website offline

    Several organisations took their websites offline this week as a precaution. That is safe, but every day offline costs inquiries and visibility.

Response time

The attackers were faster than the patch

Today the gap between a flaw becoming known and being exploited is hours, not weeks. What matters is not whether your website gets patched at some point, but how fast. Every hour in between is an open window.

  1. 17.10.2026
    First exploitation attempt observed, four days before disclosure
  2. 20.10.2026
    Details leak, the flaw is public
  3. 21.10.2026 07:43
    First attacks reported, before any fix exists
  4. 21.10.2026 14:00
    PHP releases the fixed versions
  5. ?
    Your website is patched. When was that for you?

The real question: who patches your website?

Many companies noticed this week that they could not do anything themselves. Website, access and know-how sit with an agency or a hoster. You file a ticket and wait. That is no reproach to the agency, it is a question of how you are set up.

Website run by a third party

  1. Flaw becomes known
  2. File a ticket, wait, follow up, wait
  3. Patched, eventually

Your own stack, maintained together

  1. Flaw becomes known
  2. Your team or we patch right away, the access is there
  3. Back to work. The coffee is still warm.
For your IT

The checklist to forward

If your website runs on PHP, forward this section to your IT or your agency. Updating the CMS alone is not enough, PHP itself has to be updated.

  1. 01 Check the PHP version (php -v) and update to 8.2.35, 8.3.36, 8.4.27 or 8.5.12.
  2. 02 Restart PHP-FPM or Apache. Only then is the fix actually running.
  3. 03 Still on PHP 8.1 or older? There are no official releases. Use your distribution's packages or move to a supported branch. PHP 7.3 and older get no fix at all.
  4. 04 Remove temporary mitigations (memory_limit, session.upload_progress.enabled=0, WAF rules) after the update and check the logs for unusual multipart/form-data requests.
PHP branch Fixed version
8.58.5.12
8.48.4.27
8.38.3.36
8.28.2.35
7.4 - 8.1No official release. Source backports and distribution packages only.
5.4 - 7.3No fix. Move to a supported branch.

Sources: PHP security advisory of 21 October 2026, Tenable, Sansec. As of 23 October 2026.

Example for Debian/Ubuntu
php -v
sudo apt update && sudo apt install --only-upgrade 'php8.3*'
sudo systemctl restart php8.3-fpm   # or: apache2
// Disclaimer

Warning: we are biased

We write C# in our sleep, talk about .NET at conferences and would probably recommend a toaster built on .NET. So read the next section with a wink. But do read it.

And honestly: .NET is not immune

In October 2025 ASP.NET Core had CVE-2025-55315, rated CVSS 9.9, the highest score the framework ever received. Every platform has flaws. The difference is who owns the code, who has access and how fast the patch goes live. That is exactly where our model comes in.

Cooperation

Your website. Your stack. Your control.

We migrate your PHP CMS to an open source CMS on .NET, such as Umbraco or Oqtane. Not as a black box that ends up sitting with us instead, but set up so that you stay the owner and we work alongside you as a partner.

PHP website at a third party
Your cloud, your repository
  • Website (Umbraco on .NET)
  • Customer portal (.NET)
  • Internal apps (.NET)
The website moves to where your other .NET applications already run.
  • Open source, 0 CHF licence

    Umbraco and Oqtane are open source and run on current .NET. No licence fees and no vendor holding on to you.

  • Code and hosting stay with you

    The website runs in your cloud and the code lives in your repository. Access and know-how stay in-house, even if we were gone tomorrow.

  • One stack for everything

    If you already run .NET applications, your team can look after the website too. Same language, same tools and, if you like, one single sign-on.

  • Customizable down to the detail. It is .NET, after all.

    Umbraco and Oqtane are not closed construction kits. Custom content types, blocks and editor extensions, integrations with your ERP, CRM or your own APIs: we write them in C# with the same tools as any other .NET application. No plugin zoo, just normal, testable code in your repository.

  • We stay at your side

    We build together with your team, pass on our knowledge and take care of updates and further development within a clear monthly budget. When something is on fire, whoever is there first patches it.

What this looks like is shown by a current proof of concept: an existing PHP website rebuilt on Umbraco and .NET, with a multilingual editor, preview and automatic redirects from the old URLs. We cannot show the details publicly yet. A live demo in a call, we can.

How we work

Three steps, fixed prices

You keep the costs under control and decide after every step whether to go on.

  1. 01 · Small fixed price

    Design and scope

    Together we review your current website: what stays, what goes, what is new. The result is a clear scope and a binding offer.

  2. 02 · Fixed price

    Migration and build

    Content, page structure and URLs move to the new CMS, including the agreed extensions. A reserve for small changes is planned in.

  3. 03 · Time and materials, capped monthly

    Operations and development

    Updates, security patches and new wishes. Billed by effort, with a fixed monthly ceiling. Your team can take over at any time.

Proof of concept first. Then you decide.

Who patches your website? Let's talk.

Let's Build Something Great Together

Have a question or want to discuss a project? We'd love to hear from you. Fill out the form below and we'll get back to you as soon as possible.

186 / 2000
or

You can also reach us directly at [email protected]