How a worldwide PHP issue could affect UK SMEs

Lots and lots about this PHP issue on both the mainstream media and social media, but what is it all about and how does it effect SMEs? Most people just want a straight description of the issue, a discussion on who it effects and who needs t be worried, and how to fix it. Perhaps just as importantly for SMEs, who is responsible for fixing it? I say that because the vast majority of SMEs will have outsourced their website, not just its design but also its hosting. The argument there, in regard to who needs to do the fixing, will probably come down to Ts and Cs.
So, what’s it all about? The security flaw has been dubbed PHP2Shell, and was discovered in PHP, a programming language used by around 70% of the world’s websites, including many built using WordPress.
The flaw could, and note the word could, allow hackers to break into a vulnerable website’s server remotely, without needing a password. Once inside, they could potentially steal customer information, install malicious software, change website content or use the server to launch further attacks.
Why is it in the news now? Frankly anything with the acronym AI will get an immediate hype, which is not to say there isn’t a danger, just that it will get more attention than most other, somewhat boring, security flaws which crop up all the time. So, what we’re sayi8ng is that AI techniques have been used to help identify and demonstrate the vulnerabilities. Emergency security updates were released on 21 October 2026, and reports of attempts to exploit the flaws have already surfaced. Website owners are being urged to update urgently.
A widespread PHP issue could have a significant impact on SMEs, but the level of risk depends on how the website is built, what it connects to, and how the business uses it.
The important distinction is between a website that simply provides information and one that processes orders, payments or customer information. Both can suffer disruption, but the consequences can be very different.
Two types of SME website
The first can be described as an information website. That is a website that presents services, company details and contact information, with perhaps a contact form. A website of this kind has a lower direct network exposure and ff hosted separately and isolated from the SME’s internal network, then a compromise would not automatically mean the business network has been compromised. However, the site could still be unavailable, defaced, used for phishing or have contact data stolen.
An e-commerce-enabled website however is a different problem. This is a website that accepts orders, processes customer information, manages stock or integrates with payment and fulfilment systems. It will have a much higher business impact if compromised. In addition to downtime, an incident could affect transactions, customer data, order integrity, payment integrations and the business’s ability to fulfil orders.
The key point is that a website can be separate from the office network but still be an important business asset and an entry point for attacks against customers, suppliers or connected services.
The first thing and SME needs to decide then, is what type of website they have, before they can begin to assess the risk.
What is happening with the current PHP issue?
The current incident is more serious than a routine website outage. On 21 October 2026, PHP developers released urgent security fixes for two critical vulnerabilities that could allow attackers to execute malicious code remotely on vulnerable servers without logging in. The UK’s National Cyber Security Centre (NCSC) has advised organisations to identify PHP systems, prioritise internet-facing systems, apply updates and consider taking systems offline if they cannot be secured promptly.
This means there are two separate risks for an SME:
- Availability risk: the hosting provider or website developer may temporarily take the website offline to protect it or install updates.
- Security risk: if the website remains vulnerable and is successfully attacked, the consequences could extend beyond the website itself.
The fact that the website is small or only informational does not make the PHP vulnerability irrelevant. The flaw exists at the PHP server level, rather than necessarily in a particular website feature.
Scenario A — An informational website with a contact form
Consider a small UK accountancy practice, solicitor, manufacturer or financial adviser with a website hosted by an external provider. The website has no direct connection to its Microsoft 365 environment, office computers or internal systems.
Risk 1: Website unavailable
Visitors cannot find services, verify the business’s details or submit enquiries. The immediate impact is lost leads, reduced credibility and possible disruption to customer communications.
Risk 2: Website compromised
An attacker who successfully exploits a vulnerable server might alter pages, redirect visitors to fraudulent sites, host malware or use the website to distribute phishing messages.
Risk 3: Contact-form abuse or data exposure
A form could be abused to send spam or fraudulent messages. If submissions are stored on the server, or the website has access to customer information, that information could also be at risk.
Risk 4: Potential onward attack
If the compromised website shares a hosting account with other sites, contains reusable administrator credentials, or has access to other services, the attacker may have opportunities to go further.
Does isolation from the business network protect the SME?
It materially reduces the risk, but it does not eliminate it.
If the website is genuinely isolated, runs on separate hosting and holds no internal credentials, a successful attack against it does not automatically give an attacker access to the SME’s office network.
However, isolation needs to be real, not assumed. The SME should establish whether the website:
- Uses separate hosting and administrator accounts.
- Has any integration with Microsoft 365, CRM, email marketing or cloud storage.
- Stores contact-form submissions or customer records.
- Shares hosting, credentials or administrative access with other systems.
A static informational site with a third-party contact form and no sensitive, stored data may have a relatively limited direct business impact. A WordPress website with administrator access, stored submissions and multiple integrations could present a much larger risk, despite looking like an ordinary brochure website.
Scenario B — An e-commerce-enabled website
An e-commerce website presents a more substantial business risk because it processes transactions and usually has more extensive application functionality.
Lost revenue
If the shop is taken offline, customers cannot order. Even a short interruption can cause lost sales, abandoned baskets and additional customer-service work.
Customer and order information
Depending on the websites permissions and architecture, an attacker might access customer names, addresses, contact details, order histories or other stored information.
Payment and checkout integrity
A compromised site could potentially have checkout pages altered to capture payment details or redirect customers. The actual exposure depends on whether payment processing is handled entirely by a separate provider or partly by the SME’s website.
Operational disruption
Orders might be delayed, stock records altered or integrations with fulfilment, accounting and customer-management systems disrupted.
There is also a reputational and regulatory dimension. If personal data is compromised, the SME may need to investigate the incident, assess its UK GDPR obligations and notify the ICO or affected individuals where legally required. A payment-related incident may also trigger obligations under the business’s payment-provider or acquiring-bank arrangements.
One important distinction: using a third-party payment processor reduces the amount of payment data the SME’s website needs to handle, but it does not make a compromised website harmless. The site could still manipulate the checkout experience or mislead customers.
What should you do now?
The NCSC’s latest guidance is that businesses should contact their website developer, IT provider or hosting company, confirm that the security updates have been applied, and establish whether checks for compromise have been performed.
I would recommend the following actions for both types of website.
Questions to ask your website provider and/or hosting service.
- Identify whether PHP is used
- Ask the hosting provider or web developer if WordPress and many other content management systems use PHP.
- Confirm the security patch is installed
- Request confirmation of the PHP version, the relevant security fix and when it was applied.
- Ask whether the site was checked for compromise
- Patching alone does not establish that an attacker did not access the server beforehand.
- Review access and connected services
- Check administrator accounts, unexpected changes, integrations, stored data and shared hosting.
- Verify backups and recovery
- Ensure clean backups exist and the website can be restored if necessary.
- Escalate suspicious findings
- If there are unexplained changes, new accounts or other indicators of compromise, ask a qualified incident-response provider to investigate.
- If the website provider cannot apply the fix promptly, ask what temporary protection is in place. Taking an exposed website offline may be appropriate until it can be secured. Do not assume that a web application firewall or other perimeter protection is a substitute for the required security update.
For an e-commerce business, I would add a specific review of payment-provider integrations, checkout-page integrity, customer data access and recent orders.
How this relates to H2 Cyber Risk Advisory Services
Well, I’m sure you’ll forgive me for highlighted our services, because they have a very real play here. It is a useful example of how a Cyber Maturity Assessment (CMA) and Managed Detection and Response (MDR) complement one another.
- CMA: Establishes which externally hosted services the business depends on, who manages them, what data they hold, and whether supplier oversight, incident response and recovery arrangements are adequate.
- MDR: Provides monitoring and investigation capabilities for the systems within its agreed scope. If the website or hosting environment is outside that scope, MDR should not be presented as automatically protecting it. The provider must confirm what telemetry and response capabilities are available.
- Together: The CMA identifies gaps and prioritises improvements, while MDR can provide ongoing detection and response for the systems it covers.
The central lesson for SMEs is that a website does not need a direct connection to the office network to create a serious business risk.























Recent Comments