CVE-2024-49762: Pterodactyl Panel has plain-text logging of user passwords when two-factor authentication is disabled
Impact When a user disables two-factor authentication via the Panel, a DELETE request with their current password in a query parameter will be sent. While query parameters are encrypted when using TLS, many webservers (including ones officially documented for use with Pterodactyl) will log query parameters in plain-text, storing a user's password in plain text.
Published Oct 24, 2024 · Updated Oct 25, 2024
Affected packages
pterodactyl/panel
- Ecosystem
- Composer (PHP)
- Affected
- < 1.11.8
- Fixed in
- 1.11.8
- Check
composer show pterodactyl/panel
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
When a user disables two-factor authentication via the Panel, a DELETE request with their current password in a query parameter will be sent. While query parameters are encrypted when using TLS, many webservers (including ones officially documented for use with Pterodactyl) will log query parameters in plain-text, storing a user's password in plain text.
If a malicious user obtains access to these logs they could *potentially* authenticate against a user's account; assuming they are able to discover the account's email address or username separately.
Patches
This problem has been patched by on the 1.0-develop branch and released under v1.11.8 as a single commit on top of v1.11.7
Patch file:
Workarounds
There are no workarounds at this time. There is not a direct vulnerability within the software as it relates to logs generated by intermediate components such as webservers or Layer 7 proxies.
Updating to v1.11.8 or adding the linked patch manually are the only ways to avoid this problem.
User Notice
As this vulnerability relates to historical logging of sensitive data, users who have ever disabled 2FA on a Panel (self-hosted or operated by a company) should change their passwords and consider enabling 2FA if it was left disabled. While it's unlikely that your account will be compromised by this vulnerability, it's not impossible.
Panel administrators should consider clearing any access logs that may contain sensitive data, for Panels using NGINX, the access log is located at /var/log/nginx/pterodactyl.app-access.log.
Credited to pebblehosts.
References
- https://github.com/pterodactyl/panel/security/advisories/GHSA-c479-wq8g-57hr
- https://github.com/pterodactyl/panel/commit/75b59080e2812ced677dab516222b2a3bb34e3a4
- https://github.com/pterodactyl/panel/commit/8be2b892c3940bdc0157ccdab16685a72d105dd1
- https://nvd.nist.gov/vuln/detail/CVE-2024-49762
- https://github.com/advisories/GHSA-c479-wq8g-57hr
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-54593
Pterodactyl's improper JWT scoping allows subuser to upload files when not explicitly granted `file.create` permissions
high8.1Jul 28, 2026CVE-2026-61609
Pterodactyl's shared global rate-limit key on login and 2FA checkpoint enables unauthenticated panel-wide authentication lockout (DoS)
high7.5Jul 28, 2026GHSA-j7f5-gfqm-pcx3
Pterodactyl Panel: Client email change endpoint allows enumeration of accounts in system
medium5.5Jun 26, 2026CVE-2026-35202
Pterodactyl has a database resource limit bypass via race condition in Client API
low2.3May 26, 2026CVE-2026-26016
Pterodactyl Panel Allows Cross-Node Server Configuration Disclosure via Remote API Missing Authorization
critical9.2Feb 17, 2026GHSA-hr7j-63v7-vj7g
Pterodactyl Panel's SFTP sessions remain active after user account deletion or password change
high7.5Feb 17, 2026
