Skip to main content

CVG Solutions

Is Your Website at Risk? The Critical PHP Security Flaws Explained

October 30, 2026

Your website could be exposed to cybercriminals without you even knowing it.

Two critical vulnerabilities in PHP, the technology that powers WordPress and much of the internet, were patched on 21 October 2026. These flaws could allow attackers to run malicious code on affected web servers without logging in.

If your business relies on its website to attract customers, manage bookings or generate sales, this is something you cannot afford to ignore.

The good news? There are practical steps you can take to reduce the risk, even if you have little technical knowledge.

In this blog, we’ll explain what happened, which websites could be affected, how to check your own website and what you should do to protect your business.

What has happened, and why should small businesses care?

On 21 October 2026, the PHP project released security updates to address two critical vulnerabilities: CVE-2026-109618 and CVE-2026-109619.

Both vulnerabilities received a severity rating of 9.2 out of 10. They could allow an attacker to execute their own code on an affected server without needing to log in first. Security researchers have also published information that could help attackers exploit the flaws, increasing the urgency of applying the fixes.

So, what does that mean in plain English?

Think of your website as a shop. You might have locks on the doors, passwords protecting your accounts and security measures in place to keep unwanted visitors out.

However, a vulnerability in the software running your website can create another way in. An attacker may be able to exploit that weakness without having to break through your usual login protections.

If someone gains control of your web server, the consequences could extend beyond a defaced homepage. Depending on the server’s configuration and the access available to the attacker, your business could face data exposure, website disruption, malicious code or further compromise.

For a small business, the impact could mean lost enquiries, missed bookings, interrupted sales, reputational damage and the cost of investigating and recovering from an incident.

The important point is that updating WordPress alone will not fix these particular vulnerabilities. The issue lies in PHP itself, so the underlying PHP installation needs to be updated to a fixed version.

Is your website affected?

The answer depends on how your website is built and hosted.

WordPress websites: Pay attention

If your website runs on WordPress, you should investigate this issue as a priority.

WordPress uses PHP to operate, and the same applies to many WordPress themes, plugins and online shops built using WooCommerce.

The vulnerability exists in the PHP runtime on the server. Updating your plugins and WordPress installation is good security practice, but it does not replace the necessary PHP update.

Contact your hosting provider or website developer to establish whether your server has been patched.

What about Joomla, Drupal and Magento?

These platforms also use PHP, meaning their operators should check whether their underlying PHP installations are affected and have been updated.

The same principle applies to other PHP-based applications, including some webmail, file-sharing and database-management tools. Your business might use these without realising that PHP is involved.

What if your website is hosted on another platform?

If your website is hosted on a managed platform, you may not have direct access to its underlying PHP installation.

In these circumstances, the platform provider is generally responsible for maintaining its infrastructure. Contact the provider if you are unsure whether the vulnerability affects its services.

Don’t assume every service connected to your website is automatically covered. Third-party booking systems, payment services and other integrations may have their own infrastructure and security responsibilities.

If your business relies on an external booking or customer-management system, check that the provider has assessed the issue where relevant.

What if your website is static?

A static website serves pre-built pages rather than running PHP to generate them when visitors arrive.

If your website genuinely does not use PHP, these two particular vulnerabilities do not affect it.

However, that doesn’t mean static websites are completely immune to cyberattacks. Domain accounts, email services, content-management tools and other connected systems still need appropriate protection.

How can you tell what your website uses?

You don’t need to understand programming to start investigating.

Look for these clues:

  • WordPress login: You usually manage your website through an address ending in /wp-admin.
  • Hosting control panel: Your hosting account may use cPanel or Plesk.
  • Online shop: Your website might use WooCommerce or Magento.
  • Developer or hosting records: Your original website documentation may identify the technology and PHP version in use.

These clues are useful, but they do not conclusively establish whether your server is vulnerable.

The simplest approach is to contact your hosting provider or the person responsible for maintaining your website.

Six things to do today to protect your website

You don’t need to be a cybersecurity specialist to take action. What matters is making sure the right person checks your website and deals with any necessary updates.

  1. Contact your hosting provider

Start here.

Ask your hosting provider or website developer whether the PHP installation serving your website has been updated to address CVE-2026-109618 and CVE-2026-109619.

The reported fixed versions released on 21 October 2026 are:

  • PHP 8.5.12
  • PHP 8.4.27
  • PHP 8.3.36
  • PHP 8.2.35

Your hosting provider may use a patched package supplied through its operating system or distribution instead, so the important thing is to confirm that an appropriate fix has been applied.

Ask for written confirmation rather than assuming the update has happened automatically.

  1. Check whether your PHP version is still supported

Applying the security patch is essential, but it is also worth checking whether your website runs on a supported PHP version.

Running unsupported software can leave your website exposed to other vulnerabilities, even after the current issue has been addressed.

Upgrading an older website can sometimes cause compatibility problems with outdated themes or plugins. Your developer should assess these dependencies and test the site as part of the upgrade.

Don’t attempt a major upgrade yourself if you are unsure how to recover your website should something go wrong.

  1. Update WordPress, your theme and your plugins

Once the server-side PHP issue has been addressed, check that your WordPress installation, themes and plugins are also up to date.

Remove plugins and themes you no longer use, particularly those that are no longer maintained.

Every additional component introduces potential maintenance and security considerations. Keeping your website lean and current makes it easier to manage over time.

Remember: WordPress and plugin updates are important, but they do not replace the PHP security patch.

  1. Review passwords and login security

Following the update, review access to your website and hosting account.

Use strong, unique passwords, enable two-step verification wherever possible and remove accounts that no longer need access.

Because these vulnerabilities may expose information held in server memory, reviewing credentials and active sessions is a sensible precaution. Ask your hosting provider or developer whether password changes, session invalidation or other steps are appropriate for your particular setup.

Do not assume that applying a patch automatically removes any credentials or malicious access that might have been exposed before the update.

  1. Check for signs of compromise

Updating your website reduces the risk of further exploitation, but it does not prove that nobody accessed it before the fix was applied.

Ask your hosting provider or developer to investigate any suspicious activity, particularly if your website was running a vulnerable version for an extended period.

Warning signs can include:

  • Unexpected administrator accounts.
  • Files or website changes you do not recognise.
  • Visitors being redirected to unfamiliar websites.
  • Spam links appearing on your pages or in search results.
  • Unusual activity reported by your hosting provider.
  • Security warnings displayed when people visit your website.

These signs do not necessarily prove that this particular vulnerability was exploited, but they warrant investigation.

If you suspect a breach, contact your hosting provider or a qualified incident-response specialist promptly. Avoid simply deleting suspicious files without first considering whether evidence needs to be preserved.

  1. Make sure someone is responsible for ongoing maintenance

This is the step that often gets overlooked.

Who checks your website for security updates? Who makes sure those updates are applied? Who investigates a warning from your hosting provider?

If the answer is nobody, your business has a maintenance problem that goes beyond these two vulnerabilities.

A website can look perfectly healthy to customers while running outdated software behind the scenes.

Establish who is responsible for updates, backups, security monitoring and responding to urgent vulnerabilities. If you outsource website maintenance, make sure the service you pay for actually covers these activities.

Could your other business systems be affected?

Your website isn’t necessarily the only part of your business worth checking.

Many small businesses rely on online booking systems, customer-management platforms, accounts software, file-sharing services and specialist industry applications.

Some of these may use PHP behind the scenes, even if you never see the technology yourself.

You do not need to investigate every application personally. Instead, contact the suppliers of the systems that are essential to your day-to-day operations and ask whether they have assessed the vulnerabilities and applied any necessary fixes.

It is also worth considering what would happen if an important online service became temporarily unavailable.

Could you still record customer bookings? Could you access the information needed to complete a job? Do you have a reliable way to contact customers if your usual system stops working?

A simple contingency plan can help your business continue operating while a supplier resolves a technical issue.

Is your website secure for the long term?

This incident highlights a wider issue: website security is not a one-off task.

Installing a patch is essential when a vulnerability is discovered, but maintaining a secure website requires regular attention to software, access controls, backups and hosting arrangements.

For a small business, this means establishing a consistent approach to website security rather than reacting only when a problem makes the news.

Your arrangements should cover:

  • Security updates: Apply relevant patches promptly, particularly when critical vulnerabilities are announced.
  • Software support: Avoid relying on unsupported versions of PHP, WordPress, themes or plugins.
  • Access controls: Limit administrative access to people who genuinely need it.
  • Backups: Maintain reliable backups and test whether you can restore your website successfully.
  • Monitoring: Investigate suspicious activity and security warnings.
  • Responsibility: Make sure someone is accountable for maintaining the website and responding to incidents.
  • Incident response: Know who to contact and what steps to take if your website is compromised.

The aim is not to eliminate every possible risk. It is to reduce avoidable exposure and ensure your business can respond effectively when something goes wrong.

No website is completely risk-free, regardless of the technology used. Your domain, email, user accounts and any connected services still need appropriate security.

The bottom line: Don’t wait for a problem to appear

These PHP vulnerabilities are a timely reminder that cyber security isn’t just an issue for large organisations.

Small businesses can be affected too, particularly when their websites rely on software that has not been regularly maintained.

You don’t need to panic, and you don’t need to become a technical expert overnight. You do need to establish whether your website is affected and make sure the appropriate action is taken.

Your immediate action plan is simple:

  1. Find out whether your website runs on PHP.
  2. Ask your hosting provider whether the security fixes have been applied.
  3. Check that your PHP version is supported.
  4. Make sure your website and its components are maintained.
  5. Investigate any signs of suspicious activity.
  6. Establish who is responsible for keeping your website secure in the future.

If you haven’t checked your website recently, now is a good time to start.

Frequently asked questions

What are the PHP security vulnerabilities?

The vulnerabilities described in this article were reported as critical flaws in PHP, with fixes released on 21 October 2026. They could potentially allow attackers to execute code on affected servers without logging in.

Is my WordPress website affected?

WordPress relies on PHP, so you should ask your hosting provider whether the server running your website has been updated to a fixed version. Updating WordPress and its plugins alone will not resolve these particular vulnerabilities.

Does my website need to be taken offline?

Not necessarily. The priority is to apply the appropriate security update as quickly as possible. If your hosting provider cannot update or otherwise protect a vulnerable system promptly, ask them about appropriate temporary measures. Taking a website offline may be necessary in some circumstances, but this should be assessed with your hosting provider or security specialist.

How do I know if my website has been hacked?

Look for unexpected administrator accounts, unfamiliar files, suspicious redirects, unusual website changes or security warnings. These can have several causes, so suspicious activity should be investigated by your hosting provider or a qualified professional.

Can I protect my website simply by installing a security plugin?

A security plugin may provide useful additional protection, depending on its features, but it cannot replace the necessary PHP update. The vulnerabilities exist in the underlying PHP runtime, so the server needs to be patched or appropriately remediated.

What should I ask my hosting provider?

Ask whether the PHP installation serving your website has been patched, whether it is still supported, and whether they recommend checking for evidence of compromise. Request confirmation in writing and ask what further action is required.

How can I make my website more secure in the long term?

Keep your software supported and up to date, use strong passwords and two-step verification, maintain reliable backups, review user access and make sure someone is responsible for security monitoring and responding to vulnerabilities. Regular reviews will help you identify weaknesses before they become more serious problems.

Two critical vulnerabilities in PHP, the technology that powers WordPress and much of the internet, were patched on 21 October 2026. These flaws could allow attackers to run malicious code on affected web servers without logging in.

If your business relies on its website to attract customers, manage bookings or generate sales, this is something you cannot afford to ignore.

The good news? There are practical steps you can take to reduce the risk, even if you have little technical knowledge.

In this blog, we’ll explain what happened, which websites could be affected, how to check your own website and what you should do to protect your business.

What has happened, and why should small businesses care?

On 21 October 2026, the PHP project released security updates to address two critical vulnerabilities: CVE-2026-109618 and CVE-2026-109619.

Both vulnerabilities received a severity rating of 9.2 out of 10. They could allow an attacker to execute their own code on an affected server without needing to log in first. Security researchers have also published information that could help attackers exploit the flaws, increasing the urgency of applying the fixes.

So, what does that mean in plain English?

Think of your website as a shop. You might have locks on the doors, passwords protecting your accounts and security measures in place to keep unwanted visitors out.

However, a vulnerability in the software running your website can create another way in. An attacker may be able to exploit that weakness without having to break through your usual login protections.

If someone gains control of your web server, the consequences could extend beyond a defaced homepage. Depending on the server’s configuration and the access available to the attacker, your business could face data exposure, website disruption, malicious code or further compromise.

For a small business, the impact could mean lost enquiries, missed bookings, interrupted sales, reputational damage and the cost of investigating and recovering from an incident.

The important point is that updating WordPress alone will not fix these particular vulnerabilities. The issue lies in PHP itself, so the underlying PHP installation needs to be updated to a fixed version.

Is your website affected?

The answer depends on how your website is built and hosted.

WordPress websites: Pay attention

If your website runs on WordPress, you should investigate this issue as a priority.

WordPress uses PHP to operate, and the same applies to many WordPress themes, plugins and online shops built using WooCommerce.

The vulnerability exists in the PHP runtime on the server. Updating your plugins and WordPress installation is good security practice, but it does not replace the necessary PHP update.

Contact your hosting provider or website developer to establish whether your server has been patched.

What about Joomla, Drupal and Magento?

These platforms also use PHP, meaning their operators should check whether their underlying PHP installations are affected and have been updated.

The same principle applies to other PHP-based applications, including some webmail, file-sharing and database-management tools. Your business might use these without realising that PHP is involved.

What if your website is hosted on another platform?

If your website is hosted on a managed platform, you may not have direct access to its underlying PHP installation.

In these circumstances, the platform provider is generally responsible for maintaining its infrastructure. Contact the provider if you are unsure whether the vulnerability affects its services.

Don’t assume every service connected to your website is automatically covered. Third-party booking systems, payment services and other integrations may have their own infrastructure and security responsibilities.

If your business relies on an external booking or customer-management system, check that the provider has assessed the issue where relevant.

What if your website is static?

A static website serves pre-built pages rather than running PHP to generate them when visitors arrive.

If your website genuinely does not use PHP, these two particular vulnerabilities do not affect it.

However, that doesn’t mean static websites are completely immune to cyberattacks. Domain accounts, email services, content-management tools and other connected systems still need appropriate protection.

How can you tell what your website uses?

You don’t need to understand programming to start investigating.

Look for these clues:

  • WordPress login: You usually manage your website through an address ending in /wp-admin.
  • Hosting control panel: Your hosting account may use cPanel or Plesk.
  • Online shop: Your website might use WooCommerce or Magento.
  • Developer or hosting records: Your original website documentation may identify the technology and PHP version in use.

These clues are useful, but they do not conclusively establish whether your server is vulnerable.

The simplest approach is to contact your hosting provider or the person responsible for maintaining your website.

Six things to do today to protect your website

You don’t need to be a cybersecurity specialist to take action. What matters is making sure the right person checks your website and deals with any necessary updates.

  1. Contact your hosting provider

Start here.

Ask your hosting provider or website developer whether the PHP installation serving your website has been updated to address CVE-2026-109618 and CVE-2026-109619.

The reported fixed versions released on 21 October 2026 are:

  • PHP 8.5.12
  • PHP 8.4.27
  • PHP 8.3.36
  • PHP 8.2.35

Your hosting provider may use a patched package supplied through its operating system or distribution instead, so the important thing is to confirm that an appropriate fix has been applied.

Ask for written confirmation rather than assuming the update has happened automatically.

  1. Check whether your PHP version is still supported

Applying the security patch is essential, but it is also worth checking whether your website runs on a supported PHP version.

Running unsupported software can leave your website exposed to other vulnerabilities, even after the current issue has been addressed.

Upgrading an older website can sometimes cause compatibility problems with outdated themes or plugins. Your developer should assess these dependencies and test the site as part of the upgrade.

Don’t attempt a major upgrade yourself if you are unsure how to recover your website should something go wrong.

  1. Update WordPress, your theme and your plugins

Once the server-side PHP issue has been addressed, check that your WordPress installation, themes and plugins are also up to date.

Remove plugins and themes you no longer use, particularly those that are no longer maintained.

Every additional component introduces potential maintenance and security considerations. Keeping your website lean and current makes it easier to manage over time.

Remember: WordPress and plugin updates are important, but they do not replace the PHP security patch.

  1. Review passwords and login security

Following the update, review access to your website and hosting account.

Use strong, unique passwords, enable two-step verification wherever possible and remove accounts that no longer need access.

Because these vulnerabilities may expose information held in server memory, reviewing credentials and active sessions is a sensible precaution. Ask your hosting provider or developer whether password changes, session invalidation or other steps are appropriate for your particular setup.

Do not assume that applying a patch automatically removes any credentials or malicious access that might have been exposed before the update.

  1. Check for signs of compromise

Updating your website reduces the risk of further exploitation, but it does not prove that nobody accessed it before the fix was applied.

Ask your hosting provider or developer to investigate any suspicious activity, particularly if your website was running a vulnerable version for an extended period.

Warning signs can include:

  • Unexpected administrator accounts.
  • Files or website changes you do not recognise.
  • Visitors being redirected to unfamiliar websites.
  • Spam links appearing on your pages or in search results.
  • Unusual activity reported by your hosting provider.
  • Security warnings displayed when people visit your website.

These signs do not necessarily prove that this particular vulnerability was exploited, but they warrant investigation.

If you suspect a breach, contact your hosting provider or a qualified incident-response specialist promptly. Avoid simply deleting suspicious files without first considering whether evidence needs to be preserved.

  1. Make sure someone is responsible for ongoing maintenance

This is the step that often gets overlooked.

Who checks your website for security updates? Who makes sure those updates are applied? Who investigates a warning from your hosting provider?

If the answer is nobody, your business has a maintenance problem that goes beyond these two vulnerabilities.

A website can look perfectly healthy to customers while running outdated software behind the scenes.

Establish who is responsible for updates, backups, security monitoring and responding to urgent vulnerabilities. If you outsource website maintenance, make sure the service you pay for actually covers these activities.

Could your other business systems be affected?

Your website isn’t necessarily the only part of your business worth checking.

Many small businesses rely on online booking systems, customer-management platforms, accounts software, file-sharing services and specialist industry applications.

Some of these may use PHP behind the scenes, even if you never see the technology yourself.

You do not need to investigate every application personally. Instead, contact the suppliers of the systems that are essential to your day-to-day operations and ask whether they have assessed the vulnerabilities and applied any necessary fixes.

It is also worth considering what would happen if an important online service became temporarily unavailable.

Could you still record customer bookings? Could you access the information needed to complete a job? Do you have a reliable way to contact customers if your usual system stops working?

A simple contingency plan can help your business continue operating while a supplier resolves a technical issue.

Is your website secure for the long term?

This incident highlights a wider issue: website security is not a one-off task.

Installing a patch is essential when a vulnerability is discovered, but maintaining a secure website requires regular attention to software, access controls, backups and hosting arrangements.

For a small business, this means establishing a consistent approach to website security rather than reacting only when a problem makes the news.

Your arrangements should cover:

  • Security updates: Apply relevant patches promptly, particularly when critical vulnerabilities are announced.
  • Software support: Avoid relying on unsupported versions of PHP, WordPress, themes or plugins.
  • Access controls: Limit administrative access to people who genuinely need it.
  • Backups: Maintain reliable backups and test whether you can restore your website successfully.
  • Monitoring: Investigate suspicious activity and security warnings.
  • Responsibility: Make sure someone is accountable for maintaining the website and responding to incidents.
  • Incident response: Know who to contact and what steps to take if your website is compromised.

The aim is not to eliminate every possible risk. It is to reduce avoidable exposure and ensure your business can respond effectively when something goes wrong.

No website is completely risk-free, regardless of the technology used. Your domain, email, user accounts and any connected services still need appropriate security.

The bottom line: Don’t wait for a problem to appear

These PHP vulnerabilities are a timely reminder that cyber security isn’t just an issue for large organisations.

Small businesses can be affected too, particularly when their websites rely on software that has not been regularly maintained.

You don’t need to panic, and you don’t need to become a technical expert overnight. You do need to establish whether your website is affected and make sure the appropriate action is taken.

Your immediate action plan is simple:

  1. Find out whether your website runs on PHP.
  2. Ask your hosting provider whether the security fixes have been applied.
  3. Check that your PHP version is supported.
  4. Make sure your website and its components are maintained.
  5. Investigate any signs of suspicious activity.
  6. Establish who is responsible for keeping your website secure in the future.

If you haven’t checked your website recently, now is a good time to start.

Frequently asked questions

What are the PHP security vulnerabilities?

The vulnerabilities described in this article were reported as critical flaws in PHP, with fixes released on 21 October 2026. They could potentially allow attackers to execute code on affected servers without logging in.

Is my WordPress website affected?

WordPress relies on PHP, so you should ask your hosting provider whether the server running your website has been updated to a fixed version. Updating WordPress and its plugins alone will not resolve these particular vulnerabilities.

Does my website need to be taken offline?

Not necessarily. The priority is to apply the appropriate security update as quickly as possible. If your hosting provider cannot update or otherwise protect a vulnerable system promptly, ask them about appropriate temporary measures. Taking a website offline may be necessary in some circumstances, but this should be assessed with your hosting provider or security specialist.

How do I know if my website has been hacked?

Look for unexpected administrator accounts, unfamiliar files, suspicious redirects, unusual website changes or security warnings. These can have several causes, so suspicious activity should be investigated by your hosting provider or a qualified professional.

Can I protect my website simply by installing a security plugin?

A security plugin may provide useful additional protection, depending on its features, but it cannot replace the necessary PHP update. The vulnerabilities exist in the underlying PHP runtime, so the server needs to be patched or appropriately remediated.

What should I ask my hosting provider?

Ask whether the PHP installation serving your website has been patched, whether it is still supported, and whether they recommend checking for evidence of compromise. Request confirmation in writing and ask what further action is required.

How can I make my website more secure in the long term?

Keep your software supported and up to date, use strong passwords and two-step verification, maintain reliable backups, review user access and make sure someone is responsible for security monitoring and responding to vulnerabilities. Regular reviews will help you identify weaknesses before they become more serious problems.

Two critical vulnerabilities in PHP, the technology that powers WordPress and much of the internet, were patched on 21 October 2026. These flaws could allow attackers to run malicious code on affected web servers without logging in.

If your business relies on its website to attract customers, manage bookings or generate sales, this is something you cannot afford to ignore.

The good news? There are practical steps you can take to reduce the risk, even if you have little technical knowledge.

In this blog, we’ll explain what happened, which websites could be affected, how to check your own website and what you should do to protect your business.

What has happened, and why should small businesses care?

On 21 October 2026, the PHP project released security updates to address two critical vulnerabilities: CVE-2026-109618 and CVE-2026-109619.

Both vulnerabilities received a severity rating of 9.2 out of 10. They could allow an attacker to execute their own code on an affected server without needing to log in first. Security researchers have also published information that could help attackers exploit the flaws, increasing the urgency of applying the fixes.

So, what does that mean in plain English?

Think of your website as a shop. You might have locks on the doors, passwords protecting your accounts and security measures in place to keep unwanted visitors out.

However, a vulnerability in the software running your website can create another way in. An attacker may be able to exploit that weakness without having to break through your usual login protections.

If someone gains control of your web server, the consequences could extend beyond a defaced homepage. Depending on the server’s configuration and the access available to the attacker, your business could face data exposure, website disruption, malicious code or further compromise.

For a small business, the impact could mean lost enquiries, missed bookings, interrupted sales, reputational damage and the cost of investigating and recovering from an incident.

The important point is that updating WordPress alone will not fix these particular vulnerabilities. The issue lies in PHP itself, so the underlying PHP installation needs to be updated to a fixed version.

Is your website affected?

The answer depends on how your website is built and hosted.

WordPress websites: Pay attention

If your website runs on WordPress, you should investigate this issue as a priority.

WordPress uses PHP to operate, and the same applies to many WordPress themes, plugins and online shops built using WooCommerce.

The vulnerability exists in the PHP runtime on the server. Updating your plugins and WordPress installation is good security practice, but it does not replace the necessary PHP update.

Contact your hosting provider or website developer to establish whether your server has been patched.

What about Joomla, Drupal and Magento?

These platforms also use PHP, meaning their operators should check whether their underlying PHP installations are affected and have been updated.

The same principle applies to other PHP-based applications, including some webmail, file-sharing and database-management tools. Your business might use these without realising that PHP is involved.

What if your website is hosted on another platform?

If your website is hosted on a managed platform, you may not have direct access to its underlying PHP installation.

In these circumstances, the platform provider is generally responsible for maintaining its infrastructure. Contact the provider if you are unsure whether the vulnerability affects its services.

Don’t assume every service connected to your website is automatically covered. Third-party booking systems, payment services and other integrations may have their own infrastructure and security responsibilities.

If your business relies on an external booking or customer-management system, check that the provider has assessed the issue where relevant.

What if your website is static?

A static website serves pre-built pages rather than running PHP to generate them when visitors arrive.

If your website genuinely does not use PHP, these two particular vulnerabilities do not affect it.

However, that doesn’t mean static websites are completely immune to cyberattacks. Domain accounts, email services, content-management tools and other connected systems still need appropriate protection.

How can you tell what your website uses?

You don’t need to understand programming to start investigating.

Look for these clues:

  • WordPress login: You usually manage your website through an address ending in /wp-admin.
  • Hosting control panel: Your hosting account may use cPanel or Plesk.
  • Online shop: Your website might use WooCommerce or Magento.
  • Developer or hosting records: Your original website documentation may identify the technology and PHP version in use.

These clues are useful, but they do not conclusively establish whether your server is vulnerable.

The simplest approach is to contact your hosting provider or the person responsible for maintaining your website.

Six things to do today to protect your website

You don’t need to be a cybersecurity specialist to take action. What matters is making sure the right person checks your website and deals with any necessary updates.

  1. Contact your hosting provider

Start here.

Ask your hosting provider or website developer whether the PHP installation serving your website has been updated to address CVE-2026-109618 and CVE-2026-109619.

The reported fixed versions released on 21 October 2026 are:

  • PHP 8.5.12
  • PHP 8.4.27
  • PHP 8.3.36
  • PHP 8.2.35

Your hosting provider may use a patched package supplied through its operating system or distribution instead, so the important thing is to confirm that an appropriate fix has been applied.

Ask for written confirmation rather than assuming the update has happened automatically.

  1. Check whether your PHP version is still supported

Applying the security patch is essential, but it is also worth checking whether your website runs on a supported PHP version.

Running unsupported software can leave your website exposed to other vulnerabilities, even after the current issue has been addressed.

Upgrading an older website can sometimes cause compatibility problems with outdated themes or plugins. Your developer should assess these dependencies and test the site as part of the upgrade.

Don’t attempt a major upgrade yourself if you are unsure how to recover your website should something go wrong.

  1. Update WordPress, your theme and your plugins

Once the server-side PHP issue has been addressed, check that your WordPress installation, themes and plugins are also up to date.

Remove plugins and themes you no longer use, particularly those that are no longer maintained.

Every additional component introduces potential maintenance and security considerations. Keeping your website lean and current makes it easier to manage over time.

Remember: WordPress and plugin updates are important, but they do not replace the PHP security patch.

  1. Review passwords and login security

Following the update, review access to your website and hosting account.

Use strong, unique passwords, enable two-step verification wherever possible and remove accounts that no longer need access.

Because these vulnerabilities may expose information held in server memory, reviewing credentials and active sessions is a sensible precaution. Ask your hosting provider or developer whether password changes, session invalidation or other steps are appropriate for your particular setup.

Do not assume that applying a patch automatically removes any credentials or malicious access that might have been exposed before the update.

  1. Check for signs of compromise

Updating your website reduces the risk of further exploitation, but it does not prove that nobody accessed it before the fix was applied.

Ask your hosting provider or developer to investigate any suspicious activity, particularly if your website was running a vulnerable version for an extended period.

Warning signs can include:

  • Unexpected administrator accounts.
  • Files or website changes you do not recognise.
  • Visitors being redirected to unfamiliar websites.
  • Spam links appearing on your pages or in search results.
  • Unusual activity reported by your hosting provider.
  • Security warnings displayed when people visit your website.

These signs do not necessarily prove that this particular vulnerability was exploited, but they warrant investigation.

If you suspect a breach, contact your hosting provider or a qualified incident-response specialist promptly. Avoid simply deleting suspicious files without first considering whether evidence needs to be preserved.

  1. Make sure someone is responsible for ongoing maintenance

This is the step that often gets overlooked.

Who checks your website for security updates? Who makes sure those updates are applied? Who investigates a warning from your hosting provider?

If the answer is nobody, your business has a maintenance problem that goes beyond these two vulnerabilities.

A website can look perfectly healthy to customers while running outdated software behind the scenes.

Establish who is responsible for updates, backups, security monitoring and responding to urgent vulnerabilities. If you outsource website maintenance, make sure the service you pay for actually covers these activities.

Could your other business systems be affected?

Your website isn’t necessarily the only part of your business worth checking.

Many small businesses rely on online booking systems, customer-management platforms, accounts software, file-sharing services and specialist industry applications.

Some of these may use PHP behind the scenes, even if you never see the technology yourself.

You do not need to investigate every application personally. Instead, contact the suppliers of the systems that are essential to your day-to-day operations and ask whether they have assessed the vulnerabilities and applied any necessary fixes.

It is also worth considering what would happen if an important online service became temporarily unavailable.

Could you still record customer bookings? Could you access the information needed to complete a job? Do you have a reliable way to contact customers if your usual system stops working?

A simple contingency plan can help your business continue operating while a supplier resolves a technical issue.

Is your website secure for the long term?

This incident highlights a wider issue: website security is not a one-off task.

Installing a patch is essential when a vulnerability is discovered, but maintaining a secure website requires regular attention to software, access controls, backups and hosting arrangements.

For a small business, this means establishing a consistent approach to website security rather than reacting only when a problem makes the news.

Your arrangements should cover:

  • Security updates: Apply relevant patches promptly, particularly when critical vulnerabilities are announced.
  • Software support: Avoid relying on unsupported versions of PHP, WordPress, themes or plugins.
  • Access controls: Limit administrative access to people who genuinely need it.
  • Backups: Maintain reliable backups and test whether you can restore your website successfully.
  • Monitoring: Investigate suspicious activity and security warnings.
  • Responsibility: Make sure someone is accountable for maintaining the website and responding to incidents.
  • Incident response: Know who to contact and what steps to take if your website is compromised.

The aim is not to eliminate every possible risk. It is to reduce avoidable exposure and ensure your business can respond effectively when something goes wrong.

No website is completely risk-free, regardless of the technology used. Your domain, email, user accounts and any connected services still need appropriate security.

The bottom line: Don’t wait for a problem to appear

These PHP vulnerabilities are a timely reminder that cyber security isn’t just an issue for large organisations.

Small businesses can be affected too, particularly when their websites rely on software that has not been regularly maintained.

You don’t need to panic, and you don’t need to become a technical expert overnight. You do need to establish whether your website is affected and make sure the appropriate action is taken.

Your immediate action plan is simple:

  1. Find out whether your website runs on PHP.
  2. Ask your hosting provider whether the security fixes have been applied.
  3. Check that your PHP version is supported.
  4. Make sure your website and its components are maintained.
  5. Investigate any signs of suspicious activity.
  6. Establish who is responsible for keeping your website secure in the future.

If you haven’t checked your website recently, now is a good time to start.

Frequently asked questions

What are the PHP security vulnerabilities?

The vulnerabilities described in this article were reported as critical flaws in PHP, with fixes released on 21 October 2026. They could potentially allow attackers to execute code on affected servers without logging in.

Is my WordPress website affected?

WordPress relies on PHP, so you should ask your hosting provider whether the server running your website has been updated to a fixed version. Updating WordPress and its plugins alone will not resolve these particular vulnerabilities.

Does my website need to be taken offline?

Not necessarily. The priority is to apply the appropriate security update as quickly as possible. If your hosting provider cannot update or otherwise protect a vulnerable system promptly, ask them about appropriate temporary measures. Taking a website offline may be necessary in some circumstances, but this should be assessed with your hosting provider or security specialist.

How do I know if my website has been hacked?

Look for unexpected administrator accounts, unfamiliar files, suspicious redirects, unusual website changes or security warnings. These can have several causes, so suspicious activity should be investigated by your hosting provider or a qualified professional.

Can I protect my website simply by installing a security plugin?

A security plugin may provide useful additional protection, depending on its features, but it cannot replace the necessary PHP update. The vulnerabilities exist in the underlying PHP runtime, so the server needs to be patched or appropriately remediated.

What should I ask my hosting provider?

Ask whether the PHP installation serving your website has been patched, whether it is still supported, and whether they recommend checking for evidence of compromise. Request confirmation in writing and ask what further action is required.

How can I make my website more secure in the long term?

Keep your software supported and up to date, use strong passwords and two-step verification, maintain reliable backups, review user access and make sure someone is responsible for security monitoring and responding to vulnerabilities. Regular reviews will help you identify weaknesses before they become more serious problems.

Not sure where to start with protecting your business and its data? Contact us at info@cvgsolutions.co.uk to discuss your risks, responsibilities and practical next steps.

#CyberSecurity #WebsiteSecurity #WordPressSecurity #DataProtection #SmallBusiness #BusinessResilience #CVGSolutions