# CVE-2026-97063: X-SpringBoot through 6.0 Authentication Bypass via Login Code

> Attackers can hijack user accounts by retrieving verification codes from unauthenticated API responses and using them to log in.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-vff2-49vx-fx6p

## What is CVE-2026-97063?

CVE-2026-97063 is a critical authentication bypass vulnerability in yzcheng90 X-SpringBoot, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

X-SpringBoot through 6.0 returns login verification codes in HTTP responses from unauthenticated endpoints GET /sys/mobile/code and GET /sys/email/code without sending them to account owners. Attackers can request codes using known mobile numbers or email addresses, read them from responses, and authenticate as victims via POST /sys/emailOrMobileLogin/login to hijack accounts.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-97063 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97063 is a critical authentication bypass vulnerability in yzcheng90 X-SpringBoot, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-97063 exists.

Affected product: yzcheng90 X-SpringBoot. 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-97063/ (Markdown: https://insights.sbomify.com/CVE-2026-97063/index.md)
```

## Sources

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

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