Host Hobbit now runs a daily security watch across our own hosting estate, checking official vulnerability alerts and known actively exploited issues that can affect common web technologies such as PHP, WordPress, WooCommerce, cPanel, Apache, Nginx, LiteSpeed and database services.
When something relevant appears, it is reviewed and flagged immediately so we can check the affected hosting platform and coordinate the right response. Alerts are sent directly to our technical team rather than being buried in an inbox.
Read-only monitoring · Alerts for review · Manual remediation coordination
OUR SECURITY WATCH WORKFLOW
01
Read official advisories
PHP notices and relevant CISA KEV entries.
02
Match the account inventory
Check relevance to our own hosting account.
03
Raise an alert
Flag items that need human review.
04
Verify and coordinate
Manually check patch status and next steps.
Daily monitoring and direct alerts. Patch-status checks and remediation are coordinated separately.
HOW THE SECURITY WATCH WORKS
Relevant security information, connected to our hosting inventory.
A security headline does not tell you whether a particular website is affected. Our daily watch connects credible advisories with the software recorded in our hosting account, so our technical team can identify what needs investigation.
01 / SOURCES
Read trusted notices
The monitoring correlates our inventory with official PHP security advisories and relevant entries in CISA’s Known Exploited Vulnerabilities catalogue. KEV highlights vulnerabilities known to have been exploited; it is not a list of every new or unknown flaw.
02 / RELEVANCE
Match the software
Relevant technologies include PHP, WordPress, WooCommerce, cPanel, Apache, Nginx, LiteSpeed and database services. A technology appearing in an advisory does not mean every site uses it or is vulnerable. Version and configuration details need checking.
03 / ALERTS
Flag what needs review
Relevant findings are reviewed and flagged immediately, with alerts sent directly to our technical team. The watch is read-only and alert-only: it does not install patches or modify customer sites.
04 / ACTION
Verify the patch status
Alerts initiate manual checks of the hosting platform’s patch status and remediation coordination. That means establishing whether a fix is already deployed, whether a provider backport applies, or whether further action needs arranging.
HOW FAST CAN THIS HELP?
Active now. Checking daily. A direct route to the technical team.
Our security watch runs daily. When it identifies something relevant, the finding is reviewed and flagged immediately so our technical team can check the affected platform and coordinate the right response.
An alert and a completed patch are different milestones. The daily watch helps us prioritise action. The time to resolve an issue depends on patch availability, the hosting provider and the work required for the affected website.
The watch checks relevant vulnerability advisories and known exploited issues against our own hosting inventory. Daily checks are not continuous, real-time detection.
Direct alerts for review
Relevant findings go directly to our technical team so they can verify patch status and coordinate a response. An alert does not itself mean that a website has been patched.
The right response for the issue
Provider updates, compatibility checks or other remediation may be needed. There is no automatic patching or guaranteed patch-turnaround SLA.
ZERO-DAYS, IN PLAIN ENGLISH
Monitoring disclosures is not discovering every unknown flaw.
A zero-day is a vulnerability discovered or exploited before the software supplier has a fix available. Monitoring official notices helps identify disclosed issues; it cannot guarantee discovery of vulnerabilities that have not been reported.
This workflow does not scan the wider internet for exploitable websites, test attacks against customer sites or generate and install its own fixes. Its scope is read-only correlation of security information with Host Hobbit’s own hosting inventory.
If no patch exists, any temporary protection needs separate assessment and coordination. An advisory match is not proof that a site is vulnerable, and an absence of alerts is not proof that it is secure.
WHY PATCH-STATUS VERIFICATION MATTERS
21–22 OCTOBER 2026
A real example: the critical PHP updates.
Two PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619, prompted emergency security releases. This was a server-software issue: updating WordPress alone would not resolve it.
21 OctoberPHP published fixed releases: 8.2.35, 8.3.36, 8.4.27 and 8.5.12.
21 October · 21:01 BSTOur hosting provider reported its rollout complete across all platforms, including fixes backported to older PHP versions.
22 OctoberHost Hobbit reviewed its hosting account against the fixed releases and provider confirmation, recording verification limits separately.
The patches were delivered by our hosting provider. Host Hobbit’s account review checked coverage; older versions relied on the provider’s backport confirmation. This was a separate account audit, not evidence of automatic patching by the security watch.
Yes. Our daily security watch is active now across Host Hobbit’s hosting estate. It runs every day and is read-only and alert-only. Relevant findings are reviewed and flagged directly to our technical team. Monitoring helps identify what needs checking; it is not a guarantee that every vulnerability will be detected or that a patch has already been applied.
Will it automatically patch customer websites?
No. It is read-only and alert-only. Alerts initiate manual hosting-platform patch-status verification and remediation coordination. Hosting-provider updates are separate from this monitoring workflow.
Which websites and software are in scope?
The scope is Host Hobbit’s own hosting account inventory. It considers relevant advisories for PHP, WordPress, WooCommerce, cPanel, Apache, Nginx, LiteSpeed and database services. Inclusion in that list is not a claim that each technology is installed on every site, or that external hosting accounts are covered.
What is CISA KEV?
The Known Exploited Vulnerabilities catalogue records vulnerabilities with evidence of exploitation. It helps prioritise attention, but it does not include every vulnerability or establish whether a particular website is affected.
Is there a dashboard or a guaranteed response time?
The watch runs daily and sends relevant alerts directly to our technical team. There is no public monitoring dashboard or guaranteed patch-turnaround SLA. This page explains the service; it is not a live incident-status feed.
Does monitoring replace website maintenance?
No. Monitoring supplies information. Software updates, backups, access controls and compatibility checks still need appropriate arrangements. See our WordPress help and care services.
Worried about a security alert?
Send us your website address and the advisory. We’ll explain what needs checking in plain English.