Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-69197: CWE-287: Improper Authentication in pterodactyl panel

0
Medium
VulnerabilityCVE-2025-69197cvecve-2025-69197cwe-287cwe-294
Published: Tue Jan 06 2026 (01/06/2026, 00:44:23 UTC)
Source: CVE Database V5
Vendor/Project: pterodactyl
Product: panel

Description

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.

AI-Powered Analysis

AILast updated: 01/06/2026, 01:07:35 UTC

Technical Analysis

CVE-2025-69197 is an authentication bypass vulnerability classified under CWE-287 (Improper Authentication) and CWE-294 (Authentication Bypass). It affects Pterodactyl panel, an open-source game server management tool, in versions prior to 1.12.0. The vulnerability arises because the system allows a Time-based One-Time Password (TOTP) token to be used multiple times during its validity window of approximately 60 seconds. Normally, after a user enters a valid TOTP token during login, the system should mark that token as used to prevent replay within the same time window. However, due to improper state management, the token remains valid for reuse. An attacker who intercepts a valid 2FA token—potentially by observing a screen share or other side-channel—can reuse the token to authenticate as the user without needing to generate a new token or perform additional authentication steps. The CVSS v3.1 base score is 6.5 (medium severity), reflecting network attack vector, low attack complexity, requiring privileges (valid username/password), no user interaction, unchanged scope, high confidentiality impact, and no impact on integrity or availability. No known exploits are currently reported in the wild. The vulnerability is resolved in Pterodactyl panel version 1.12.0, which properly invalidates TOTP tokens after use within their validity window.

Potential Impact

For European organizations using Pterodactyl panel versions 1.11.11 or earlier, this vulnerability poses a risk of unauthorized account access despite 2FA being enabled. Attackers who can intercept a valid TOTP token can bypass the intended second factor, potentially gaining access to game server management interfaces. This could lead to unauthorized control over game servers, data exposure, or disruption of services. While the vulnerability does not directly affect data integrity or availability, unauthorized access could enable further malicious activities such as data exfiltration or service manipulation. Organizations relying on Pterodactyl for critical infrastructure or customer-facing services may face reputational damage and operational risks. The impact is heightened in environments where screen sharing or token exposure is common, such as remote administration or support scenarios. Given the medium CVSS score and the requirement for token interception, the threat is moderate but should not be underestimated.

Mitigation Recommendations

European organizations should immediately upgrade all Pterodactyl panel instances to version 1.12.0 or later to ensure the vulnerability is patched. In addition, organizations should implement strict operational security measures to prevent interception of 2FA tokens, including limiting screen sharing sessions, using secure communication channels, and educating users on protecting authentication credentials. Monitoring and logging authentication attempts can help detect suspicious reuse of tokens. Where possible, consider implementing additional layers of authentication or anomaly detection to flag unusual login patterns. Regularly review and audit user access and 2FA configurations to ensure compliance with best practices. Finally, organizations should maintain an incident response plan to quickly address potential compromises resulting from this vulnerability.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-12-29T14:34:46.743Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 695c5ce23839e44175a692c0

Added to database: 1/6/2026, 12:52:50 AM

Last enriched: 1/6/2026, 1:07:35 AM

Last updated: 1/8/2026, 11:23:33 AM

Views: 21

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats