All reports
Medium

NocoDB: Refresh Tokens Persist Through Password Recovery

Affected versions

Affected versions
<= 0.301.3
Fixed version
Not reported

Exploitation

CVE-2026-53928

Probability of exploitation in the next 30 days: 0.36%

FIRST EPSS · 2026-11-18

Description

Summary

A stolen refresh token survived a password-forgot flow and could be used to mint fresh JWTs even after the user reset their password.

Details

passwordChange and passwordReset deleted the user's refresh tokens, but passwordForgot only rotated token_version and revoked OAuth tokens — it did not call UserRefreshToken.deleteAllUserToken(user.id). An attacker holding a captured refresh cookie could still exchange it for a new access token after the victim triggered the recovery flow.

Impact

Persistent unauthorized access after password recovery. Once a refresh token leaks, the documented "Forgot password" recovery flow did not in fact revoke the attacker's session.

Credit

This issue was reported by @bugbunny-research.

Links

Credits

  • bugbunny-research