Checked on 23 October 2026. Security guidance can change. Follow the linked vendor advisories for subsequent updates.

Your website may still load, take enquiries and look completely normal while the software underneath it needs an urgent security update. For a business that relies on bookings, orders or customer information, that is a reason to get a clear answer from the host today.

The PHP project has released fixes for two critical vulnerabilities, commonly called PHP2Shell. Under applicable conditions, an attacker can execute code on an affected server without signing in. The PHP team urges users to update immediately. Read the official PHP security announcement.

What was found?

PHP is software that runs many websites on their servers. These flaws are in that runtime, underneath the website application.

VulnerabilityPlain-English explanationVendor severity
CVE-2026-109618An out-of-memory error can interrupt setup of internal request data. Later cleanup can use that incomplete data incorrectly, potentially allowing remote code execution.Critical: CVSS 4.0 score 9.2/10
CVE-2026-109619Internal references can survive after their memory has been freed. Later processing can use that stale state, potentially exposing memory or enabling remote code execution.Critical: CVSS 4.0 score 9.2/10

Actual exploitability depends on the deployment and execution path. PHP reports a demonstrated attack against Apache with mod_php before application code runs. An application login or a WordPress security plugin therefore cannot be relied on as the fix for those paths. PHP’s deployment and mitigation guidance.

Does the “70%” headline mean my site is vulnerable?

The headline describes PHP’s broad use. W3Techs reported PHP on 69.3% of websites whose server-side programming language it could identify on 21 October 2026. That is a technology-usage estimate, not a measurement of compromised or currently unpatched sites. Your own status needs checking. W3Techs usage data and survey context.

A WordPress logo, a .php address or a public scan result alone cannot establish that your host is running a vulnerable build. Equally, a working website or a hidden version number is not evidence that the update has been applied.

Which PHP versions contain the fix?

These are the first fixed releases in the supported branches listed by PHP. Use an appropriate fixed release or later security update:

PHP branchFirst fixed release
8.28.2.35
8.38.3.36
8.48.4.27
8.58.5.12

Source: PHP’s affected and patched version list. Some operating-system or hosting vendors backport fixes into packages with an older-looking version number. Ask for the vendor advisory and package build, rather than deciding from the version string alone. Older branches need explicit vendor coverage or a supported upgrade plan. Datadog’s deployment guidance.

Updating WordPress alone does not update the server’s PHP

WordPress says these issues are not specific to WordPress and require no WordPress release of their own. It directs owners to check the PHP version under Tools → Site Health → Info → Server and coordinate with the hosting provider. Use that screen as a starting point for the conversation, not a substitute for package-level patch confirmation. WordPress security notice.

If another company manages your website, forward the request below to them and the host. Ask one named person to take responsibility for closing the loop.

Copy this message to your hosting provider

Different websites, subdomains or hosting settings can use different PHP installations. Datadog’s remediation guidance calls for checking each deployment, applying the appropriate package or image update, and restarting or replacing workers still running the old runtime. Read the remediation steps.

Keep the website useful while the fix is applied

Agree a backup and rollback plan with the person doing the work. Then test the functions your business depends on: signing in, sending an enquiry, making a booking, checking out, uploading a document and receiving the expected email. Record the result and who will resolve anything that fails. This is BusiQuip’s proposed business acceptance checklist for a scoped update.

If an update cannot happen promptly, ask your provider about protections before requests reach PHP, such as restricting access or isolating the affected application. The UK NCSC advises considering taking systems offline where updates or temporary mitigations cannot be applied promptly. These decisions should be made with the responsible administrator. NCSC guidance.

Cloudflare says it has deployed PHP2Shell WAF protections for free and paid customers. Check the current rules and whether all relevant traffic passes through that protection. A WAF is an interim layer, not a replacement for updating the affected runtime. Cloudflare’s protection announcement.

A patch is not proof that an earlier intrusion has been removed

If you find unexpected administrator accounts, altered files or other suspicious activity, tell your hosting or security provider and preserve the relevant evidence. Do not assume installing the update also removes an existing backdoor. The NCSC specifically calls for compromise assessment where systems cannot be updated or disabled immediately. Read the incident-response advice.

Get a clear answer and an agreed plan

BusiQuip can help Eswatini businesses work through a website security check and scope the next steps with their hosting provider. The aim is practical: establish patch status, arrange authorised remediation where needed, and check that the website still supports the business.

Request a quote on WhatsApp: +268 7878 0709, or contact BusiQuip. Share your website address and hosting provider if known; do not send passwords. The scope and fee are agreed before work begins. Legacy upgrades, recovery after a breach and ongoing maintenance may need separate work.

A PHP patch check covers specified issues at a point in time; it does not make a website immune to every attack. Continue with our “Black October” business protection checklist, explore cybersecurity services, or browse more BusiQuip guides.