Technical impact
The vulnerability in Apache SeaTunnel Web 1.0.2 permits a disabled user account to be authenticated again by creating a new login token, bypassing the intended account-status check. The login endpoint fails to verify that the account is disabled, so valid credentials continue to work. This flaw allows an attacker who possesses the disabled account's credentials to perform authenticated requests against protected APIs, potentially accessing sensitive data or internal services. The weakness is an authentication bypass (CWE-287).
Affected Systems
Affected product is Apache SeaTunnel Web version 1.0.2 from the Apache Software Foundation. No other versions are noted, and the source indicates that this release is no longer maintained and contains no fixes for the account status check added in pull request #264. Because the component is unsupported, there is no official fixed release available.
Risk and Exploitability
The vulnerability requires valid credentials for the disabled account; it is not a credential-free bypass. The EPSS score is not available and the issue is not listed in the CISA KEV catalog, so the likelihood of exploitation cannot be quantified objectively. However, if an attacker obtains a victim's disabled account credentials through phishing, credential reuse, or a prior breach, they can bypass the account lockout and gain access to internal APIs. The exploitation path is straightforward: submit the blocked user's real username and password to the login endpoint, receive a new token, and use that token to make authorized requests. The overall risk depends largely on the strength of the disabled account passwords and the sensitivity of the protected API endpoints.