HotGo's Mobile Login Path Needs Its Own Asset and Identity Review
HotGo deployments combine a web administration interface with mobile login and SMS workflows. An external inventory should cover both the product page and the identity endpoint behind it.
ZoomEye count-only queries used sub_type=all, page 1 and page size 1 on 2026-11-13 between 07:40 and 07:43 Asia/Shanghai.
| Query | Matching assets |
|---|---|
app="HotGo" |
499 |
title="HotGo" |
384 |
The close counts do not prove that the application string and title identify the same hosts. They provide two candidate sets for ownership and version checks.
The login issue
CVE-2026-120447 affects HotGo 2.8.4 through 2.15.1. The advisory says an unauthenticated attacker can choose the verification code by supplying the Code field to /admin/sms/send, then sign in through /admin/site/mobileLogin.
The attacker needs a target mobile number. A successful login can take over an administrator account, so the SMS endpoint is part of the authentication boundary. The advisory does not claim that a matching ZoomEye host has been compromised.
Triage the candidates
Confirm which matches are live HotGo installations and which are documentation, demos, reseller pages or unrelated text. For each owned instance, record the version, the mobile login path and the accounts allowed to use SMS.
Review whether the public endpoint accepts a caller-supplied code. Test in a controlled environment and confirm that the server generates, stores and expires the value independently of the client.
Inspect authentication logs for short send-to-login intervals, new administrator sessions and phone-number changes. Compare the source IP and device context with the account's normal behavior.
Reduce reachability
Restrict administration and mobile login endpoints to trusted networks or an identity-aware proxy. Disable SMS login for privileged users until a fixed build is confirmed.
The upstream commit referenced by the advisory is cb57056c746650e6ff86dec1e97d404b63dcfd30. Administrators should verify which release includes it rather than treating the affected range as a complete patch guide.
What ZoomEye adds
The app and title queries narrow the external search to a few hundred candidates. That makes it practical to ask owners for a version and authentication-path confirmation. The counts do not reveal the SMS provider, the list of privileged accounts or whether a code-generation flaw is present.
Keep the candidate, owned, version-confirmed and compromised states separate in the inventory. A product name in an HTML title is not enough to open a confirmed incident.
Top comments (0)