Nginx UI is a web user interface for the Nginx web server. Prior to 2.4.1, GenerateShortToken creates standalone short-token records without a long Token value, but DeleteUserTokens invalidates cached entries only when the long Token field is nonempty. A revoked short token can therefore remain in the short_token cache and authenticate again if the associated account is re-enabled before the cache entry expires because GetTokenUserByShortToken reads the surviving entry, restoring access to HTTP or WebSocket routes that accept short-token authentication. This issue is fixed in version 2.4.1.

Affected: Go: github.com/0xJacky/Nginx-UI

### Summary Standalone short tokens issued for WebSocket and explicit-token authentication can survive administrative revocation in cache. If the same account is later re-enabled before the cache entry expires, the deleted short token becomes valid again.

### Details `GenerateShortToken()` creates an `AuthToken` row that contains only `ShortToken` and no long `Token`. `DeleteUserTokens()` removes database rows, but when clearing caches it only invalidates entries where `authToken.Token != ""`. This leaves standalone short-token cache entries behind. `GetTokenUserByShortToken()` checks that cache first and then loads the user by ID, so the stale short token becomes usable again if the account status is restored to `true`.

Relevant code paths: - [internal/user/user.go](/home/kali/Desktop/bounty/nginx-ui/internal/user/user.go:43) - [internal/user/user.go](/home/kali/Desktop/bounty/nginx-ui/internal/user/user.go:118) - [internal/user/user.go](/home/kali/Desktop/bounty/nginx-ui/internal/user/user.go:204) - [api/user/short_token.go](/home/kali/Desktop/bounty/nginx-ui/api/user/short_token.go:13) - [internal/middleware/middleware.go](/home/kali/Desktop/bounty/nginx-ui/internal/middleware/middleware.go:82)

### PoC This was verfied locally in an isolated environment with a temporary package-level harness that exercised the real token issuance, revocation, cache, and re-authentication paths.

What the executed test did: 1. Created an enabled user in a temporary SQLite database. 2. C…