Menu

HotGo's Mobile Login Path Needs Its Own Asset and Identity Review
📰

HotGo's Mobile Login Path Needs Its Own Asset and Identity Review

DEV Community·Ioneyrezende·6 days ago
#5CAooc8y
#dev#login#hotgo#mobile#zoomeye
Reading 0:00
15s threshold

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.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.