همهٔ گزارش‌ها
متوسط

NocoDB: Refresh Tokens Persist Through Password Recovery

متن اصلی

نسخه‌های متأثر

نسخه‌های متأثر
<= 0.301.3
نسخهٔ اصلاح‌شده
اعلام نشده

بهره‌برداری

CVE-2026-53928

احتمال بهره‌برداری در ۳۰ روز آینده: 0.36%

FIRST EPSS · ۱۴۰۵/۰۸/۲۶

شرح آسیب‌پذیری

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.

پیوندها

گزارش‌دهندگان

  • bugbunny-research