Pterodactyl vulnerable to 2FA Sniffing

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2019-1020002: 1.47% estimated exploitation activity in the next 30 days; percentile 73.86 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Pterodactyl version 0.7.13 and lower - 2FA Sniffing Users who have enabled 2FA protections on their account can unintentionally have their account's existence sniffed by malicious users who enter random credentials into the login fields. Impact Users who have enabled 2FA protections on their account can unintentionally have their account's existence sniffed by malicious users who enter random credentials into the login fields. A logical mistake was made when the original code was written that would wait to verify the user's password until they had provided 2FA credentials if it was enabled on their account. However, because of this you could enter a bad password for a known email and determine if the account exists if you got redirected to a 2FA page. For more information If you have any questions or comments about this advisory please react out on Discord or email dane@[project name].io.

Published by the source

24 May 2022, 16:51 UTC

Last modified by the source

1 Feb 2023, 05:06 UTC

Source last checked

26 Oct 2026, 14:04 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-fg52-xjfc-9rh8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2019-1020002

Advisory: Pterodactyl vulnerable to 2FA Sniffing
IDs: CVE-2019-1020002, GHSA-fg52-xjfc-9rh8
Record: https://patchnext.com/advisories/cve-2019-1020002 (revision 1, source checked 26 Oct 2026, 14:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: pterodactyl/panel 0.7.14. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist pterodactyl/panel: affected <= 0.7.13; fixed in 0.7.14

## Suggested inspection (read-only)
- Packagist pterodactyl/panel: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pterodactyl/panel.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-fg52-xjfc-9rh8 (GitHub-reviewed advisory GHSA-fg52-xjfc-9rh8 lists affected ranges: Packagist pterodactyl/panel >=0 <=0.7.13)

Commands are suggestions: review each one before running it.