Skip to main content
GNS Technology Limited logo

PHP2Shell: why websites that have not been updated in years should rebuild

Anson Ng Anson Ng 3 min read

In October 2026 the PHP project issued a rare emergency security release, fixing two remote code execution (RCE) vulnerabilities rated 9.2 (CVSS v4.0) — CVE-2026-109618 and CVE-2026-109619, now known as "PHP2Shell". An attacker needs no authentication to run arbitrary code on an affected server, which is effectively the same as taking over the whole machine.

The real danger: older PHP versions get no fix

The official fixes only cover still-supported releases: PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP 8.1 and all earlier versions are end-of-life and will not receive a patch.

That means a website that has not been touched for eight or ten years — still running PHP 5.x, 7.x or older — cannot simply "patch later". There is no patch to install. Those sites usually carry several problems at once:

  • outdated frameworks and libraries, with one vulnerability after another
  • plugins and components that nobody maintains any more
  • non-compliant data handling and security settings
  • poor mobile experience and poor visibility in AI search

WordPress sites are affected too

WordPress is one of the world's most widely used website platforms, and it runs on PHP. PHP2Shell is a flaw in the PHP runtime itself — it has nothing to do with any individual plugin or theme. As long as the underlying PHP is unpatched, a WordPress site is exposed in the same way as Joomla, Drupal or a custom PHP system.

Updating WordPress to the latest version does not by itself make a site immune; what matters is the PHP version running on the host:

  • If the host has upgraded to PHP 8.2.35 / 8.3.36 / 8.4.27 / 8.5.12 or newer, the risk is fixed.
  • If the site still runs PHP 8.1 or earlier, there is no official patch, and the site stays exposed.

For WordPress sites left on an old host for years without maintenance, the situation is usually worse: an old PHP version, old plugins and an old theme constrain each other, and upgrading can break the site. That is exactly why rebuilding on a PHP-free stack is often the cheaper, safer choice.

Patching cannot fix an old system — rebuilding can

Patching one vulnerability at a time does not change the fact that the underlying stack is obsolete. For a company, the more practical move is to rebuild the site on a modern, PHP-free stack:

  • Static site: generated with a modern framework such as Astro, with no PHP runtime on the server, so PHP-class vulnerabilities simply do not apply.
  • Faster and safer: static output behind a CDN is fast, has a smaller attack surface, and is easier to back up and deploy.
  • Content you control: the company can update articles, solutions and product information itself.

Add GEO while you rebuild

A rebuild is the right moment to also fix AI-search visibility. GEO (generative engine optimization) makes your brand the one that AI assistants such as Gemini, Doubao and Perplexity cite and recommend. A well-structured new site with consistent facts and FAQ schema is exactly the foundation GEO needs.

To an AI engine, a legacy website is often outdated, fragmented information. After the rebuild, your brand has a real chance to become the recommended answer.

How GNS helps

GNS Technology is a Hong Kong systems integrator and web development company. We can start from an audit and rebuild from scratch:

  1. audit the existing website and systems, then determine the risk and the next step
  2. rebuild the site on a modern, PHP-free stack
  3. migrate existing content and preserve your SEO assets
  4. build FAQ schema, entity data and consistent content for GEO
  5. provide maintenance and technical support after launch

If your website has not been updated for years, or is still running an old PHP version, now is the time to act. See enterprise web development, GEO services or talk to us on WhatsApp.

FAQ

Is our current website affected by PHP2Shell?

If the site runs on PHP — including WordPress, Joomla, Drupal and custom PHP systems — it is at risk whenever the underlying PHP has not been updated to a fixed release (8.2.35 / 8.3.36 / 8.4.27 / 8.5.12 or newer). PHP 8.1 and earlier are end-of-life and receive no official patch.

Can GNS inspect our existing website or system?

Yes. GNS audits existing websites and systems: we review the technology stack, PHP / framework / plugin versions, security settings and compliance posture, then recommend whether to patch, migrate or rebuild.

Why is updating WordPress not necessarily enough?

PHP2Shell is a flaw in the PHP core, not in WordPress itself. Updating WordPress does not fix the underlying PHP runtime; the host's PHP version is what has to be upgraded.

Can GEO be added while rebuilding the site?

Yes. GNS adds FAQ schema, consistent entity data and structured content to the new site, making the brand easier for AI search such as Gemini, Doubao and Perplexity to cite and recommend.

Will rebuilding lose existing content and SEO?

No. GNS migrates the existing content and preserves your SEO assets, including URL structure, metadata and structured data.