A security alert can leave you with more questions than answers. Is your website affected? Has your hosting provider already dealt with it? And if an update has been installed, is there anything else you should check?
When you’re busy running a business, you shouldn’t have to untangle all of this alone.
What has happened?
On 21 October, the PHP project released fixes for two critical vulnerabilities that could allow attackers to take control of affected web servers.
PHP powers WordPress and many other websites. These vulnerabilities are in PHP itself: updating WordPress, themes or plugins alone will not fix them. Your hosting provider or server administrator needs to address the PHP installation.
Read the WordPress security announcement
Start with your hosting provider
Ask them to confirm:
- Whether your website or any other PHP services on your account are affected.
- Whether the relevant fixes have been installed and are active.
- Whether older software needs further attention.
- What action remains, and who is responsible for it.
The PHP security releases are 8.2.35, 8.3.36, 8.4.27 and 8.5.12. Some providers deliver fixes through their own maintained packages, so a version number alone may not tell the whole story.
PHP also published follow-up guidance on 23 October about an additional risk in an unusual configuration. Ask your provider to check that advice alongside the original updates. If patching cannot happen promptly, discuss appropriate temporary protections, including whether affected services should be taken offline.
Read PHP’s official security notices
Patching matters. So does understanding what happened before it.
Applying the fixes is essential, but it does not establish whether a website was accessed before the update.
Depending on the circumstances, further checks may include reviewing logs, unfamiliar administrator accounts, unexpected file changes and other signs of suspicious activity.
Vulnerability scans can help identify remaining weaknesses. Investigating a possible compromise may require additional checks. A clean scan is useful evidence, but it cannot guarantee that nothing happened.
How CareFront can help
CareFront can help you understand where things stand through vulnerability scans, clear reports and practical guidance on what needs attention next.
That might mean helping you interpret a report, identifying unresolved weaknesses, or working with your existing technical team to prioritise follow-up checks.
We’ll explain what has been checked, what the findings mean and where further investigation may be needed.
If your hosting provider has already resolved the issue, that’s a good outcome. If you’re still unsure, you’re welcome to start a conversation with CareFront about the support you need.
You deserve clear answers and practical help, without added pressure.