A critical PHP security flaw, PHP2Shell, affects many websites. Hong Kong SMEs using WordPress or online shops need to ask their web host three questions now.
- Date
- Reading
- 4 min read
- Written by
- Nick Li
- Tags
- #Risk#Web#Engineering
Imagine your online shop or company website suddenly goes blank, or worse, shows something completely unexpected. Many business owners worry about their website's security. This month, a critical PHP security flaw, dubbed PHP2Shell, has made those worries very real for many businesses worldwide, including in Hong Kong [1].
What is PHP2Shell and why is it a big deal?
PHP is a programming language that powers a huge part of the internet – nearly 70% of all websites whose server-side language is known [1, 4]. This includes popular platforms like WordPress, WooCommerce, and many bespoke online shops and company websites used by Hong Kong SMEs. The new flaw, called PHP2Shell, is a serious problem in PHP's core engine [1, 3, 4]. It allows attackers to run their own code on a web server without needing a password or login [1, 4]. Think of it like someone being able to walk into your shop's back office and change things, or steal files, without needing a key.
Security experts say this is one of the most severe vulnerabilities discovered in software history [1, 4]. The flaw has been present for decades, but new AI tools have made it much easier for hackers to exploit [1, 4, 5]. This means websites running unpatched versions of PHP are at immediate risk of being defaced, having data stolen, or simply going offline [1, 4]. We have seen early attacks emerging [1], making prompt action essential for Hong Kong small and medium businesses.
Three questions to ask your web agency or hosting provider today
You do not need to be a tech expert to protect your business. Here are three clear questions to ask your web agency or hosting provider right away:
-
Are our systems affected by the PHP2Shell vulnerability?
This flaw affects PHP versions from 5.4 through 8.5.11 [3, 4]. If your website uses PHP 8.1 or older, it is particularly important, as these versions are no longer officially supported and will not receive a direct fix [1, 3]. Your provider should be able to tell you your current PHP version.
-
Have the emergency patches been applied, and when?
The PHP Group released emergency patches on October 21, 2026 [3, 4]. Your provider should confirm that these patches (CVE-2026-109618 and CVE-2026-109619) have been installed on your server [2, 3]. If your site runs on an older, unsupported PHP version, ask them what their upgrade plan is. Remember, updating the operating system on the server might not be enough if your application runs in a container [3].
-
What temporary protections are active while patching is completed?
While patches are being applied, a Web Application Firewall (WAF) can offer some temporary protection by blocking known attack patterns [3]. Ask your provider if a WAF is active for your website and what specific rules are in place to block PHP2Shell exploits. This buys time, but it is not a permanent fix [3].
For a deeper look into why security is so important for your online presence, you might find our article Why most company websites should be static useful.
Different views on the problem
This vulnerability has prompted strong reactions from various groups:
-
Security firms like Wiz and OpenAI highlight how advanced AI models were crucial in discovering and exploiting these decades-old flaws, suggesting this could be a turning point for cybersecurity in the AI era [1, 4, 5]. OpenAI called it "one of the most impactful security issues in recent memory" [1].
-
The PHP Group itself has warned that basically any site running PHP is at risk and urged immediate updates [1].
-
Government agencies, such as the NSA Cybersecurity account on X and the UK’s National Cyber Security Center, have even recommended taking affected systems offline if immediate updates are not possible [1].
-
Sansec, another security firm, went further, stating they "expect mass attacks to start within 15 minutes of the release" of the patches [2].
These views underscore the urgency of addressing this issue.
What your business should do today
Here are the immediate steps you should take:
-
Contact your web agency or hosting provider with the three questions above.
-
Confirm their patching schedule and ensure it is happening quickly.
-
Ask about temporary firewall protections and verify they are active.
-
If your site handles sensitive customer data or financial transactions, consider temporarily disabling non-essential features or even the site itself until you receive confirmation that it is fully patched and secure [1].
-
Keep a record of your conversations and the actions taken.
This is a serious issue, but with prompt action, you can protect your business. If you are unsure how to proceed or need help communicating with your providers, let's talk.
