Blogs

PHP2Shell: What Happened, Why Websites Went Offline, and How Organizations Should Respond

  • 1st Jan 1970
🛡️ Cybersecurity Advisory

Published: October 29, 2026 | By One Cover Pvt. Ltd.

Two critical vulnerabilities in PHP, collectively nicknamed PHP2Shell, surfaced in October 2026[cite: 16]. Triggering emergency defensive responses worldwide, organisations across Nepal temporarily took their web applications offline to apply vital security patches[cite: 16].

Executive Summary & Key Takeaways

  • The Core Threat: Flaws CVE-2026-109618 & CVE-2026-109619 allow unauthenticated remote command execution on vulnerable web servers[cite: 16].
  • National Impact: High-profile government portals, Nepal Rastra Bank, and commercial banking web services underwent temporary preventative outages[cite: 16].
  • Global Coordination: Similar protective shutdowns occurred simultaneously in Finland, the Netherlands, Japan, and the UK[cite: 16].
  • Immediate Mandate: Enterprises must verify their underlying PHP package versions and patch immediately[cite: 16].

What is PHP2Shell?

PHP2Shell refers to two critical vulnerabilities (CVE-2026-109618 and CVE-2026-109619) found deep within the core framework of PHP[cite: 16]. Because PHP underpins nearly 70 percent of all identifiable websites globally, the scope of exposure is vast[cite: 16]. Both flaws carry a severe CVSS score of 9.2 out of 10, enabling unauthenticated attackers to execute arbitrary system commands on underlying web servers[cite: 16].

Crucially, because the flaw exists inside PHP itself rather than application scripts, even immaculately coded websites built on popular CMS platforms like WordPress, Joomla, Drupal, or Magento remain inherently vulnerable if running an unpatched runtime environment[cite: 16].

Timeline of the Crisis

Date Event Overview Status
20 October 2026 Vulnerability details became public before official fixes were fully deployed[cite: 16]. Disclosure
21 October 2026 PHP released emergency security patches (versions 8.5.12, 8.4.27, 8.3.36, and 8.2.35). Nepal's NCSC issued advisories[cite: 16]. Patch Release
22 October 2026 Major Nepali government portals, NRB, and commercial banks went offline as a precaution[cite: 16]. Precautionary Shutdown
25–26 October 2026 SDOC patched shared platforms, bringing thousands of websites back online safely[cite: 16]. Restoration Phase

Why Taking Sites Offline Was a Responsible Step

Cybersecurity frameworks recommend immediate patching; where instant patching is impossible, taking systems offline remains a recognized defensive safeguard[cite: 16]. Attackers mobilized immediately following disclosure. Media reports citing Cloudflare telemetry highlighted tens of thousands of automated attack attempts within just 45 minutes of the news breaking, alongside confirmed exploitation in the wild[cite: 16]. Pausing public availability prevented potential automated server compromises.

What Organizations Should Do Now

  1. Check Your PHP Version Today: Confirm you are running patched releases (8.5.12, 8.4.27, 8.3.36, 8.2.35) or a vendor-backported package[cite: 16]. Obtain written confirmation from your hosting provider[cite: 16].
  2. Plan for End-of-Life Versions: PHP 8.1 no longer receives security updates, and PHP 8.2 reaches end-of-life on December 31, 2026[cite: 16]. Migrate to fully supported branches proactively.
  3. Remember Patched Does Not Mean Clean: Because exploitation started within hours[cite: 16], inspect servers for anomalous PHP worker processes, unknown files in temporary directories, or unexpected outbound traffic. Always preserve logs and server snapshots before cleanup[cite: 16].
  4. Rotate Credentials: If exposure is suspected, immediately update stored database passwords, API tokens, and access keys[cite: 16].
  5. Prepare Incident Response Plans: Document clear protocols for who holds authority to pause a service, how to notify users, and how to safely restore operations[cite: 16].

What the General Public Should Know

A scheduled website outage for security patching is distinct from a confirmed data breach; reports have not indicated citizen data loss resulting from the PHP2Shell response[cite: 16]. Users are advised to rely strictly on official channels and avoid entering sensitive login or financial details onto unverified lookalike domains during temporary public service disruptions[cite: 16].

Conclusion

As Nepal’s digital ecosystem continues expanding across banking, public services, and governance, maintaining software integrity is paramount[cite: 16]. Routine patching, supported version management, and robust response readiness safeguard both digital availability and user trust[cite: 16].

About One Cover

One Cover Pvt. Ltd. delivers comprehensive Vulnerability Assessment and Penetration Testing (VAPT), web application security reviews, and tactical cybersecurity advisory services[cite: 16]. If your enterprise operates PHP-based infrastructure and requires an expert security posture review, get in touch with our team today.