Skip to main content
Vulnerability Database/CVE-2026-97064

CVE-2026-97064: X-SpringBoot Authentication Bypass Flaw

CVE-2026-97064 is an authentication bypass flaw in X-SpringBoot through version 6.0 caused by a hardcoded master login code. Attackers can authenticate as any user using the static code 172839. This article covers technical details, affected versions, security impact, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-97064 Overview

X-SpringBoot through version 6.0 contains a hardcoded static master login verification code (172839) enabled by default in the database seed. Unauthenticated attackers can authenticate as any user by submitting this public master code to the emailOrMobileLogin endpoint along with a known email address or mobile number. The flaw bypasses the SMS and email one-time code verification intended to protect account authentication. The vulnerability is classified under CWE-1392: Use of Default Credentials and affects any X-SpringBoot deployment running the default seed data.

Critical Impact

Any unauthenticated attacker who knows a user's email or mobile number can take over the account by submitting the public master code 172839 to the login endpoint.

Affected Products

  • X-SpringBoot through 6.0 (yzcheng90/X-SpringBoot)
  • Default database seed deployments using x_springboot.sql
  • Any instance exposing the emailOrMobileLogin endpoint

Discovery Timeline

  • 2026-09-25 - CVE-2026-97064 published to the National Vulnerability Database (NVD)
  • 2026-09-30 - Last updated in NVD database

Technical Details for CVE-2026-97064

Vulnerability Analysis

X-SpringBoot ships with an authentication path that accepts either a user-supplied SMS or email verification code, or a static master code preloaded in the database. The master code (172839) is embedded in the project's seed SQL file and shipped publicly in the repository. Because the value is identical across every default installation, it functions as a universal backdoor credential.

The SysLoginController validates the submitted verification code against the stored master code before issuing a session token. When the submitted value matches 172839, the controller treats the login as valid without any further checks against a per-user SMS or email code. An attacker needs only the target's email address or mobile number to complete authentication.

The issue falls under CWE-1392: Use of Default Credentials. Since the credential is static and public, exploitation requires no brute force or cryptographic weakness.

Root Cause

The root cause is the inclusion of a plaintext master verification code in the default database seed file doc/x_springboot.sql. The application's login handler accepts this value as equivalent to a legitimate per-session one-time code. Operators who deploy X-SpringBoot without manually removing the seeded master record inherit the backdoor on first run.

Attack Vector

Exploitation is remote and unauthenticated over the network. An attacker enumerates or guesses a valid email address or mobile number, then sends a POST request to the emailOrMobileLogin endpoint containing the target identifier and the static code 172839. The server returns an authenticated session token for the targeted account, including administrative accounts if the attacker targets an admin email or phone number.

A public proof-of-concept is available in the LinYuanyi1 cve-request-poc repository. Additional technical analysis is published in the VulnCheck advisory. The vulnerable logic can be reviewed in the SysLoginController source and the seeded SQL file.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-97064

Indicators of Compromise

  • Successful logins to the emailOrMobileLogin endpoint where the submitted verification code equals 172839.
  • Authentication events for administrative or privileged accounts originating from unrecognized IP addresses.
  • Login attempts enumerating a broad range of email addresses or mobile numbers from a single source.
  • Session tokens issued without a preceding SMS or email code generation request in the audit log.

Detection Strategies

  • Inspect application logs for POST requests to emailOrMobileLogin and alert when the verification code field contains the literal 172839.
  • Deploy a web application firewall rule that blocks or logs requests to the login endpoint containing the known master code.
  • Audit the sys_user and related tables in the X-SpringBoot schema for the presence of a static master code entry seeded from x_springboot.sql.

Monitoring Recommendations

  • Enable verbose authentication logging on all X-SpringBoot instances, including the submitted code field (hashed if required by policy).
  • Forward authentication events to a centralized log platform and alert on repeated successful logins across distinct accounts from one source IP.
  • Track account takeover indicators such as password resets, email changes, or role modifications following a login event.

How to Mitigate CVE-2026-97064

Immediate Actions Required

  • Remove or invalidate the master verification code record in the application database, specifically the entry inserted from doc/x_springboot.sql at line 147.
  • Restrict external access to the emailOrMobileLogin endpoint until the master code logic is removed from SysLoginController.
  • Rotate credentials and session tokens for any accounts that may have been accessed since the application was deployed.
  • Review authentication logs for prior use of the code 172839 and treat any matching sessions as compromised.

Patch Information

No official vendor patch has been published at the time of CVE assignment. Operators should modify the SysLoginController login flow to remove the master-code comparison and ensure that only per-session SMS or email codes are accepted. Refer to the X-SpringBoot repository for upstream changes and the VulnCheck advisory for mitigation guidance.

Workarounds

  • Delete the seeded master verification code row from the database and verify it is not re-inserted by application startup logic.
  • Place the application behind an authenticated reverse proxy or VPN to limit exposure of the login endpoint.
  • Apply a WAF signature that rejects any login request where the verification code equals 172839.
  • Enforce strict rate limiting on the emailOrMobileLogin endpoint to slow enumeration of valid email addresses and mobile numbers.
bash
# Example WAF rule (ModSecurity) blocking the known master code
SecRule REQUEST_URI "@endsWith /emailOrMobileLogin" \
  "id:1026097064,phase:2,deny,status:403,\
   chain,msg:'CVE-2026-97064 X-SpringBoot master code blocked'"
  SecRule ARGS "@streq 172839" "t:none"

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.