PHP2Shell : See if you’re affected with a free external attack surface scan. Click Here > 

New CVE Detected

CVE-2026-97064 – Authentication Bypass (Default Master Code) – X-SpringBoot ≤ 6.0

Be the first to know when new zero-days emerge:

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 emailOrMobileLogin endpoint in SysLoginController.java validates 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 emailOrMobileLogin endpoint and related verification-code validation logic in SysLoginController.java to 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 emailOrMobileLogin requests against multiple accounts, which may indicate exploitation attempts.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge