Medium

Pterodactyl Panel has plain-text logging of user passwords when two-factor authentication is disabled

  • Disclosed: 24.10.2024
  • Updated: 11.10.2026 10:22

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 https://github.com/pterodactyl/panel/commit/8be2b892c3940bdc0157ccdab16685a72d105dd1 on the 1.0-develop branch and released under v1.11.8 as a single commit on top of v1.11.7 https://github.com/pterodactyl/panel/commit/75b59080e2812ced677dab516222b2a3bb34e3a4

Patch file: https://github.com/pterodactyl/panel/commit/8be2b892c3940bdc0157ccdab16685a72d105dd1.patch

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.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Composer package pterodactyl/panel < 1.11.8 1.11.8

References

CVSS score 4.6/10
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N
Weakness (CWE)
CWE-313
Platform
Composer
Package
pterodactyl/panel
Disclosed
24.10.2024
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-c479-wq8g-57hr - CC BY 4.0

Vulnerability history: pterodactyl/panel

All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (19) in the archive
Total entries
19
First → latest
10.2020 07.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • Critical 2
  • High 6
  • Medium 8
  • Low 3

Disclosures per year

  1. 2020: 1
  2. 2021: 3
  3. 2022: 2
  4. 2023: 0
  5. 2024: 2
  6. 2025: 2
  7. 2026: 9
Severity:
  1. Critical · 10.0 CVE-2025-49132 < 1.11.11 1.11.11
  2. Pterodactyl Panel has plain-text logging of user passwords when two-factor authentication is disabled this entry
    Medium · 4.6 CVE-2024-49762 < 1.11.8 1.11.8
  3. High · 7.5 CVE-2019-1020002 < 0.7.14 0.7.14

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.