PHP Hit by “PHP2Shell” Critical Vulnerability: Hackers Can Remotely Take Over Servers

PHP, the programming language used by a huge share of the world’s websites, has been hit by two extremely serious security vulnerabilities collectively known as “PHP2Shell.” The flaws, identified as CVE-2026-109618 and CVE-2026-109619, both received a 9.2 out of 10 rating under the CVSS v4.0 severity scale, placing them in the critical category.

What hackers can do

The vulnerabilities relate to how PHP handles memory and manages its internal state. In certain circumstances, an attacker may be able to remotely execute malicious code on an affected server without needing a username, password, or other form of authentication.

If successfully exploited, attackers could:

  • Take control of a website or server
  • Steal customer data, passwords, and other sensitive information
  • Alter website content
  • Install malware
  • Disrupt websites or business services

How widespread is the impact?

PHP is one of the world’s most widely used server-side programming languages. According to W3Techs, around 70% of websites with a known server-side language run on PHP; popular platforms including WordPress, Drupal, and Joomla are also built on it.

This means the vulnerability does not affect just one company or website. It could potentially affect large numbers of government agencies, businesses, e-commerce platforms, media sites, and small-business websites worldwide.

Global emergency response

According to the report, governments and companies in multiple countries have rushed to patch their systems. Some government websites have even been taken offline as a precaution, choosing temporary service disruption over leaving systems exposed before patches are fully applied.

Security firms have reported the emergence of suspected exploitation tools targeting these vulnerabilities, lowering the barrier for attackers. Even where large-scale successful intrusions have not yet been confirmed, organizations should treat this as an urgent security incident.

What businesses and website administrators should do

  1. Inventory systems immediately: Identify every website, API, back-office system, hosting service, and server that uses PHP, along with its exact version.
  2. Patch immediately: Upgrade to the officially patched versions, including PHP 8.2.35, 8.3.36, 8.4.27, and 8.5.12, or later security releases in the same branches.
  3. Check vendors: If websites are managed by hosting providers, cloud platforms, or outsourced developers, immediately ask them to confirm that patches have been applied.
  4. Isolate systems that cannot be patched yet: Consider temporarily taking systems offline, restricting external access, or strengthening firewall and WAF protections. These are temporary measures, not substitutes for patching.
  5. Look for signs of compromise: Review logs for unusual logins, suspicious files, website defacements, abnormal network connections, and other indicators of compromise. If anything suspicious is found, isolate the system immediately and preserve evidence.

What this means for businesses

This incident shows how a vulnerability in a widely used foundational technology can spread rapidly across the world. For companies, website security is no longer merely a technical detail—it directly affects customer trust, business continuity, data protection, and brand reputation.

The safest approach is to verify versions immediately, apply updates immediately, and confirm that the patch is working. If legacy systems cannot be patched, organizations should decisively suspend public-facing services or isolate them rather than leave them exposed as an entry point for attackers

About the Author

Leave a Reply

Your email address will not be published. Required fields are marked *

You may also like these