By Null Ventures MCP platform
Menu

vulnerability / NVI-00005010 / Revision 3

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

OSV carries this publisher advisory for pterodactyl/panel. This is an aggregated source copy; consult the original publisher and compare update dates.

source listedactiveGHSA-c479-wq8g-57hrCVE-2024-49762

This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.

01 / Meaning

Why it matters

Published affected context helps an owner decide what evidence to gather. This report has not examined your application.

EPSS

0.141%

FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.03412. Missing scores are unknown.

As of · FIRST EPSS

02 / Applicability

The affected context

Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.

pterodactyl/panel

source listed
  • ECOSYSTEM: introduced 0; fixed 1.11.8

### 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

GitHub Advisory Database via OSV

03 / Response

What to do next

  1. vendor patch

    The original advisory lists fixed boundaries 1.11.8 for pterodactyl/panel. Confirm the publisher’s latest guidance.

    Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database via OSV

  2. investigate

    Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.

    Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. FIRST EPSS

A fixed release is not deployment evidence.

Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.

04 / Limits

What this report cannot establish

  • Customer inventory, deployment, reachability and exploitation have not been inspected.
  • NVD lastModified does not establish freshness of every associated CPE record.
Read the collection and interpretation limits ↗

05 / Provenance

Sources you can inspect

Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.

  1. GHSA-c479-wq8g-57hr ↗

    GitHub Advisory Database via OSV · vendor advisory

    Observed . GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.

  2. CVE-2024-49762 ↗

    NIST National Vulnerability Database · official catalog

    Observed . This product uses data from the NVD API but is not endorsed or certified by the NVD.

  3. CVE-2024-49762 ↗

    FIRST EPSS · official catalog

    Observed . FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.

Public revision history

Only published revisions appear here. Routine fetches do not create a material-change event.

  1. Revision 3 ·

    Source facts changed; compare the preserved prior revision.

  2. Revision 2 ·

    Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.

Read the public revision data ↗

The next step is private

Bring the question into your environment.

The connected workflow is a development preview for inventory, contextual matching, owner decisions and evidence-based verification. No system-specific result is generated by this page.

See the synthetic workflow preview ↗