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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Do first: Apply the patch listed under Evidence.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fix or patch referenced
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
Apply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- Record last updated
Affected versions
- bufanyun HotGo
From 2.8.4 · through 2.15.1
Evidence 6
- Patch
- Exploit
- Report
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120447
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: vul.yulun.ac.cn
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: vul.yulun.ac.cn
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: vul.yulun.ac.cn
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: cve.now feed data