Summary
CVE-2026-97063 is a critical improper authentication vulnerability (CWE-287) affecting X-SpringBoot through version 6.0, an open-source Spring Boot–based admin/management framework maintained by yzcheng90. The application’s unauthenticated code-request endpoints echo the actual SMS and email login verification codes back in the HTTP response instead of only dispatching them out-of-band, allowing any unauthenticated attacker who knows a victim’s phone number or email address to retrieve a valid login code and hijack the account. The flaw carries a CVSS v3.1 base score of 9.1–9.3 (Critical) given its network attack vector, low complexity, and lack of required privileges or user interaction.
Technical details
- Root cause: The endpoints
GET /sys/mobile/codeandGET /sys/email/codegenerate a one-time login code and return it directly in the JSON response body (msgCode/emailCode) rather than solely transmitting it via actual SMS/email delivery. - Trigger conditions: No authentication, session, or CAPTCHA is required to call these endpoints; the request only needs a target’s mobile number or email address, both of which are frequently guessable or harvested from other sources. The time parameter used in code generation is client-controlled and not validated server-side, and no rate limiting is enforced on code requests.
- Attack vector: Network-based, unauthenticated. An attacker requests a code for a target identifier, reads the code straight from the response, then submits it to
POST /sys/emailOrMobileLogin/loginto obtain a valid session/authentication token for that user. - Impact: Full account takeover for any user whose contact identifier (phone/email) is known, including potentially privileged or administrative accounts, since the login flow only checks the leaked code plus
status/auditStatusvalues in Redis with no additional binding to the legitimate requester.
Affected software
- X-SpringBoot (yzcheng90/X-SpringBoot), all versions through 6.0
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: As of publication, no vendor-supplied patched release has been confirmed. Security teams should monitor the yzcheng90/X-SpringBoot repository for an update that removes the verification code from the code-request API responses and delivers it only via the actual SMS/email channel, and upgrade as soon as a fixed version is released.
- If no patch is available:
- Restrict or disable public access to
/sys/mobile/code,/sys/email/code, and/sys/emailOrMobileLogin/loginat the network/WAF layer until a fix is deployed. - Implement strict rate limiting and CAPTCHA on code-request endpoints to blunt automated abuse.
- Enforce server-side, tamper-proof time/nonce validation for generated codes rather than trusting client-supplied values.
- Monitor logs for repeated or bulk requests to the code endpoints, which are a strong indicator of exploitation attempts.
- Where feasible, require an additional authentication factor beyond the SMS/email code for sensitive account actions.
- Restrict or disable public access to

