CVE-2025-69197: Pterodactyl TOTPs can be reused during validity window
Summary When a user signs into an account with 2FA enabled they are prompted to enter a token. When that token is used, it is not sufficiently marked as used in the system allowing an attacker that intercepts that token to then use it in addition to a known username/password during the token validity window.
This vulnerability requires that an attacker already be in possession of a valid username and password combination, and intercept a valid 2FA token (for example, during a screen share). The token must then be provided in addition to the username and password during the limited token validity window. The validity window is ~60 seconds as the Panel allows at most one additional window to the current one, each window being 30 seconds.
Other sources
Pterodactyl is a free, open-source game server management panel. Versions 1.11.11 and below allow TOTP to be used multiple times during its validity window. Users with 2FA enabled are prompted to enter a token during sign-in, and afterward it is not sufficiently marked as used in the system. This allows an attacker who intercepts that token to use it in addition to a known username/password during the 60-second token validity window. The attacker must have intercepted a valid 2FA token (for example, during a screen share). This issue is fixed in version 1.12.0.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-69197?
CVE-2025-69197 is classified as a medium severity vulnerability due to its potential to allow unauthorized access through repeated use of valid TOTP tokens.
How do I fix CVE-2025-69197?
To fix CVE-2025-69197, upgrade to Pterodactyl version 1.12.0 or later which addresses the vulnerability.
What versions of Pterodactyl are affected by CVE-2025-69197?
Pterodactyl versions 1.11.11 and below are affected by CVE-2025-69197.
What vulnerability does CVE-2025-69197 introduce?
CVE-2025-69197 introduces a weakness that allows tokens used for two-factor authentication to be reused within their validity period.
Is two-factor authentication secure in versions affected by CVE-2025-69197?
Two-factor authentication is compromised in affected versions of Pterodactyl as tokens can be reused, which poses a security risk.