Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-97063 – Authentication Bypass / Account Takeover – X-SpringBoot ≤ 6.0

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

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/code and GET /sys/email/code generate 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/login to 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/auditStatus values 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/login at 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.

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