Summary
CVE-2026-97064 is a critical authentication bypass vulnerability in X-SpringBoot (yzcheng90), a Spring Boot–based admin/management framework, affecting all versions through 6.0. The application ships with a hardcoded static "master" login verification code (172839) enabled by default in the database seed data, allowing unauthenticated attackers to log in as any known user. The flaw carries a CVSS v3.1 base score of 9.1 and a CVSS v4.0 score of 9.3, both rated Critical.
Technical details
- Root cause: The default database seed for X-SpringBoot includes a hardcoded "super code" / master verification code (172839) that the login flow accepts in place of a legitimate, per-user, time-limited SMS/email verification code.
- Trigger conditions: The vulnerable
emailOrMobileLoginendpoint inSysLoginController.javavalidates the submitted verification code against Redis-stored values; when the master-code override is enabled (the shipped default), submitting the static code 172839 alongside any known email address or mobile number satisfies this check regardless of the actual generated code. - Attack vector: Network — remote and unauthenticated. No prior access, credentials, or user interaction is required.
- Impact: Full authentication bypass enabling account takeover for any user whose email or mobile number is known/guessable, resulting in high confidentiality and integrity impact (attacker can act with the privileges of the impersonated account, including administrative accounts).
Affected software
- yzcheng90 X-SpringBoot: all versions through 6.0 (version range 0 ≤ 6.0), as shipped with the default database seed data.
Severity
- CVSS v3.1 Base Score: 9.1 (Critical) —
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N - CVSS v4.0 Base Score: 9.3 (Critical) —
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
Mitigation and recommended actions
- Immediate: No official patched release has been identified at the time of publication. Administrators should treat any deployment using the default X-SpringBoot database seed as compromised-by-design and remediate immediately.
- Workarounds/network mitigations:
- Remove or disable the hardcoded master verification code (172839) from the database seed/system parameters (the "super code" override) before deploying to any internet-facing environment.
- Audit the
emailOrMobileLoginendpoint and related verification-code validation logic inSysLoginController.javato enforce per-user, single-use, properly randomized codes with no static override. - Restrict external network exposure of X-SpringBoot login endpoints where possible (e.g., place behind VPN or IP allow-listing) until custom remediation is applied.
- Rotate credentials and invalidate active sessions for all accounts if the application has been internet-exposed with default seed data.
- Monitor authentication logs for login attempts using the code 172839 or repeated
emailOrMobileLoginrequests against multiple accounts, which may indicate exploitation attempts.

