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


- **Severity:** Critical 9.2 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Nov 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-c3f7-678j-f69g

## What is CVE-2026-120447?

CVE-2026-120447 is a critical vulnerability in bufanyun HotGo, published on 2 Nov 2026. 

### Official 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-120447?


## How do I fix CVE-2026-120447?

No fix has been published for CVE-2026-120447 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-120447 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120447 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120447 and fix it if it is affected.

What it is: CVE-2026-120447 is a critical vulnerability in bufanyun HotGo, published on 2 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120447 exists.

Affected product: bufanyun HotGo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120447/ (Markdown: https://insights.sbomify.com/CVE-2026-120447/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120447
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120447
- OSV: https://osv.dev/vulnerability/CVE-2026-120447

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120447/
Summaries are generated and may contain mistakes; the official description above is the record.
